This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 218619 - IllegalStateException: Still listening on org.netbeans.modules.web.webkit.debugging.api.dom.DOM@cf0082
Summary: IllegalStateException: Still listening on org.netbeans.modules.web.webkit.deb...
Status: NEW
Alias: None
Product: javascript
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 7.3
Hardware: All All
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
: 218667 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-09-19 13:41 UTC by Vladimir Riha
Modified: 2015-10-05 21:39 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 192575

Attachments
stacktrace (4.10 KB, text/plain)
2012-09-19 13:41 UTC, Vladimir Riha 		Details
stacktrace (4.10 KB, text/plain)
2012-09-20 08:47 UTC, Vladimir Riha 		Details
stacktrace (4.10 KB, text/plain)
2012-09-25 11:08 UTC, tusharvjoshi 		Details
stacktrace (4.58 KB, text/plain)
2012-12-30 11:17 UTC, dds.dhawal 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Riha 2012-09-19 13:41:45 UTC 
This bug was originally marked as duplicate of bug 216129, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE Dev (Build 201209190001)
VM: Java HotSpot(TM) Client VM, 23.3-b01, Java(TM) SE Runtime Environment, 1.7.0_07-b10
OS: Linux

User Comments:
vriha: I run html file, no idea what exactly caused it




Stacktrace: 
java.lang.IllegalStateException: Still listening on org.netbeans.modules.web.webkit.debugging.api.dom.DOM@cf0082
   at org.netbeans.modules.web.javascript.debugger.breakpoints.DOMNode.bindTo(DOMNode.java:303)
   at org.netbeans.modules.web.javascript.debugger.breakpoints.WebKitBreakpointManager$WebKitDOMBreakpointManager.add(WebKitBreakpointManager.java:271)
   at org.netbeans.modules.web.javascript.debugger.breakpoints.BreakpointRuntimeSetter.createBreakpointImpls(BreakpointRuntimeSetter.java:108)
   at org.netbeans.modules.web.javascript.debugger.breakpoints.BreakpointRuntimeSetter.<init>(BreakpointRuntimeSetter.java:88)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:0)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
Comment 1 Vladimir Riha 2012-09-19 13:41:48 UTC 
Created attachment 124583 [details]
stacktrace
Comment 2 Vladimir Riha 2012-09-20 08:47:09 UTC 
Created attachment 124627 [details]
stacktrace

running 2 projects with identical code, one has DOM breakpoint
Comment 3 Vladimir Riha 2012-09-20 08:49:00 UTC 
What seems to be reproducible (not sure if always):
- run some project and create a DOM breakpoint
- create a new project identical to the first one and  run it
- try to add the same DOMbreakpoint to the 2nd project
Comment 4 Martin Entlicher 2012-09-20 14:00:23 UTC 
*** Bug 218667 has been marked as a duplicate of this bug. ***
Comment 5 tusharvjoshi 2012-09-25 11:08:11 UTC 
Created attachment 124859 [details]
stacktrace

View file in Embedded Browser
Run File in Crome
Cancelled the debug in Crome
Comment 6 Vladimir Riha 2012-11-20 09:53:42 UTC 
Correction for report 631174:
- the fileB.html was actually in different project and run in embedded browser (while fileA.html in Chromium) - I accidentally run different file with the same name...
Comment 7 dds.dhawal 2012-12-30 11:17:14 UTC 
Created attachment 129760 [details]
stacktrace

Run HTML file
Comment 8 Vladimir Riha 2013-02-22 10:25:10 UTC 
This is reproducible with re-running project in devices (please see my latest exception report [1]). 

[1] http://statistics.netbeans.org/exceptions/exception.do?id=660165