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.
Build: NetBeans IDE Dev (Build EaselCSS-520-on-20120821) VM: Java HotSpot(TM) 64-Bit Server VM, 23.2-b09, Java(TM) SE Runtime Environment, 1.7.0_06-b24 OS: Windows 7 User Comments: jskrivanek: I closed Chrome browser. Stacktrace: java.lang.AssertionError at org.netbeans.modules.extbrowser.plugins.chrome.WebKitDebuggingTransport.sendCommand(WebKitDebuggingTransport.java:62) at org.netbeans.modules.web.webkit.debugging.TransportHelper.sendBlockingCommand(TransportHelper.java:107) at org.netbeans.modules.web.webkit.debugging.api.css.CSS.getAllStyleSheets(CSS.java:102) at org.netbeans.modules.web.inspect.webkit.ui.DocumentNode$DocumentChildFactory.createKeys(DocumentNode.java:102) at org.openide.nodes.AsynchChildren.run(AsynchChildren.java:206) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1454)
Created attachment 123332 [details] stacktrace
Created attachment 123354 [details] stacktrace 1. Run project in Chrome 2. Choose Inspect Element in Chrome popup menu - opens Chrome Tools and detaches NetBeans 3. Close the Chrome tab 4. Switch back to IDE
There was no proper handling of case when Chrome's native Developer Tools are opened. What happens is that only single client is suppoted for debugging protocol on Chrome's side. And opening native dev tools kickout NB debugging session. I'm fixing it by sending a message from browser to IDE to basically close everything from IDE's side. The behaviour now should be same as if user closed the tab being debugged by NB. I increased version of plugin to 0.4.19. Hopefully this also resolves this problem. web-main#927ce0a9be2f
*** Bug 216305 has been marked as a duplicate of this bug. ***
Created attachment 123396 [details] stacktrace Still reproducible - several times run EaselDemo project and then close Chrome browser.
This is a Page Inspector issue - after communication channel with the browser was closed the Page Inspector should not issue any other WebKit commands. This could be fixed in many ways, for example for JS debugger there is an explicit NetBeansJavaScriptDebuggerFactory.stopDebuggingSession. Passing to Honza.
Created attachment 123448 [details] stacktrace closed chrome with running page
Created attachment 123540 [details] stacktrace Closed Chrome tab.
This bug already has 5 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=191702
Created attachment 123593 [details] stacktrace
maybe issue #217369 is a duplicate of this?
Created attachment 123641 [details] stacktrace closed web page in chrome
(In reply to comment #11) > maybe issue #217369 is a duplicate of this? It is the same assert, but not the same problem. The assert checks whether a command was invoked while the debugger was "detached". The stack-trace of 217369 is different, i.e., it is a different command that was invoked (and a different piece of code must be fixed).
Fixed by http://hg.netbeans.org/web-main/rev/21cf6e25132f
Integrated into 'main-golden', will be available in build *201209031048* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/927ce0a9be2f User: David Konecny <dkonecny@netbeans.org> Log: #217128 - when native Developer Tools are opened in Chrome the NetBeans debugger is (involuntarily) detached