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.
Sometimes when the page inspection is started it takes significant time (~10s) for Browser DOM view to populate. The console shows several warnings about getDocument() returning null when the view is populated finally. The attachment shows the thread dump taken during the "freeze".
Created attachment 134360 [details] thread dump
The thread dump shows that "org.netbeans.modules.web.inspect.webkit.WebKitPageModel" thread waits in sendBlockingCommand("DOM.getDocument"). The expected response should be delivered by "WebSocketServer" thread. "WebSocketServer" thread attempts to enter DOM.handleDocumentUpdated, but it waits for DOM.this lock that is held by "org.netbeans.modules.web.inspect.webkit.WebKitPageModel" thread. This would be a deadlock if there weren't a timed wait in sendBlockingCommand(). This is a race condition. It occurs when documentUpdated event is delivered while we are waiting for response for DOM.getDocument message.
Fixed by http://hg.netbeans.org/web-main/rev/5546f36fe1c3