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 250170 - NB doesn't responde
Summary: NB doesn't responde
Status: RESOLVED FIXED
Alias: None
Product: web
Classification: Unclassified
Component: Inspection (show other bugs)
Version: 8.1
Hardware: All All
: P2 normal (vote)
Assignee: Jan Stola
URL:
Keywords:
: 248017 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-02-03 08:37 UTC by Ondrej Brejla
Modified: 2015-03-02 16:58 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread dump (30.28 KB, application/octet-stream)
2015-02-03 08:37 UTC, Ondrej Brejla 		Details
Another TD (30.10 KB, application/octet-stream)
2015-02-16 08:53 UTC, Ondrej Brejla 		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 Ondrej Brejla 2015-02-03 08:37:55 UTC 
Created attachment 151785 [details]
Thread dump

Not sure about right component, but I worked with HTML5 project :) So feel free to reassign, thanks.
Comment 1 Tomas Mysik 2015-02-03 08:50:57 UTC 
Seems to be a problem in web inspection. Honzo, please evaluate, thanks.
Comment 2 Ondrej Brejla 2015-02-16 08:53:03 UTC 
Created attachment 152005 [details]
Another TD

Happened again...
Comment 3 Jan Stola 2015-03-02 10:48:46 UTC 
The deadlock is between event-dispatch and org.netbeans.modules.web.inspect.webkit.WebKitPageModel threads.

Event-dispatch thread is trying to acquire WebKitPageModel.this lock through WebKitPageModel.getNode() method, but this lock is held by org.netbeans.modules.web.inspect.webkit.WebKitPageModel thread.

On the other hand org.netbeans.modules.web.inspect.webkit.WebKitPageModel thread is trying to enter some mutex in nodes area that is held by event-dispatch thread.

It seems that I am running in circles in this area :-(. Some time ago I fixed the same kind of deadlock (issue 216491 and issue 216955) by removal of the synchronized keyword from WebKitPageModel.getNode()'s prototype (and by making WebKitPageModel.nodes map synchronized). Unfortunately, few months ago I have added the synchronized keyword to WebKitPageModel.getNode() method again accidentally (it seems that I overlooked that the nodes map is sychronized then).

So, I am removing the synchronized keyword again.

Modified file: https://hg.netbeans.org/web-main/rev/b26c7a7bfbe0
Comment 4 Jan Stola 2015-03-02 16:58:09 UTC 
*** Bug 248017 has been marked as a duplicate of this bug. ***