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 217128 - AssertionError at org.netbeans.modules.extbrowser.plugins.chrome.WebKitDebuggingTransport.sendCommand
Summary: AssertionError at org.netbeans.modules.extbrowser.plugins.chrome.WebKitDebugg...
Status: VERIFIED FIXED
Alias: None
Product: web
Classification: Unclassified
Component: Inspection (show other bugs)
Version: 7.3
Hardware: All All
: P2 normal (vote)
Assignee: Jan Stola
URL:
Keywords:
: 216305 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-08-21 07:42 UTC by Jiri Skrivanek
Modified: 2012-09-04 13:34 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 191702


Attachments
stacktrace (1.81 KB, text/plain)
2012-08-21 07:42 UTC, Jiri Skrivanek
Details
stacktrace (1.81 KB, text/plain)
2012-08-21 15:38 UTC, Petr Jiricka
Details
stacktrace (1.81 KB, text/plain)
2012-08-22 11:05 UTC, Jiri Skrivanek
Details
stacktrace (1.81 KB, text/plain)
2012-08-23 09:14 UTC, Vladimir Riha
Details
stacktrace (1.81 KB, text/plain)
2012-08-24 13:38 UTC, Petr Jiricka
Details
stacktrace (1.81 KB, text/plain)
2012-08-27 06:49 UTC, Vladimir Riha
Details
stacktrace (1.81 KB, text/plain)
2012-08-28 08:52 UTC, Tomas Mysik
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Skrivanek 2012-08-21 07:42:01 UTC
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)
Comment 1 Jiri Skrivanek 2012-08-21 07:42:03 UTC
Created attachment 123332 [details]
stacktrace
Comment 2 Petr Jiricka 2012-08-21 15:38:26 UTC
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
Comment 3 David Konecny 2012-08-22 08:03:15 UTC
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
Comment 4 Tomas Mysik 2012-08-22 10:23:42 UTC
*** Bug 216305 has been marked as a duplicate of this bug. ***
Comment 5 Jiri Skrivanek 2012-08-22 11:05:25 UTC
Created attachment 123396 [details]
stacktrace

Still reproducible - several times run EaselDemo project and then close Chrome browser.
Comment 6 David Konecny 2012-08-22 22:15:04 UTC
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.
Comment 7 Vladimir Riha 2012-08-23 09:14:25 UTC
Created attachment 123448 [details]
stacktrace

closed chrome with running page
Comment 8 Petr Jiricka 2012-08-24 13:38:25 UTC
Created attachment 123540 [details]
stacktrace

Closed Chrome tab.
Comment 9 Exceptions Reporter 2012-08-24 13:38:31 UTC
This bug already has 5 duplicates 
see http://statistics.netbeans.org/exceptions/detail.do?id=191702
Comment 10 Vladimir Riha 2012-08-27 06:49:57 UTC
Created attachment 123593 [details]
stacktrace
Comment 11 Vladimir Riha 2012-08-27 06:51:14 UTC
maybe issue #217369 is a duplicate of this?
Comment 12 Tomas Mysik 2012-08-28 08:52:57 UTC
Created attachment 123641 [details]
stacktrace

closed web page in chrome
Comment 13 Jan Stola 2012-08-28 09:28:40 UTC
(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).
Comment 14 Jan Stola 2012-08-28 11:24:15 UTC
Fixed by http://hg.netbeans.org/web-main/rev/21cf6e25132f
Comment 15 Quality Engineering 2012-09-03 13:01:13 UTC
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