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 108705 - o.n.editor.settings deadlock
Summary: o.n.editor.settings deadlock
Status: RESOLVED DUPLICATE of bug 107400
Alias: None
Product: editor
Classification: Unclassified
Component: Settings (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Vitezslav Stejskal
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-03 01:34 UTC by err
Modified: 2007-11-05 13:42 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread dump after hang (24.32 KB, text/plain)
2007-07-03 01:35 UTC, err 		Details
messages.log after hang and forced shutdown (263.40 KB, text/plain)
2007-07-03 01:38 UTC, err 		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 err 2007-07-03 01:34:12 UTC 
With NB6M10. Selected and closed all modules in project TC. All the editors closed, the project TC was empty. IDE hung.
Attaching thread dump and messages.log

Found one Java-level deadlock:
=============================
"org.netbeans.editor.Settings.PROCESSOR":
  waiting to lock monitor 0x2f485624 (object 0x04746b18, a java.util.HashMap),
  which is held by "AWT-EventQueue-1"
"AWT-EventQueue-1":
  waiting to lock monitor 0x2f484fa4 (object 0x2376f428, a java.lang.Class),
  which is held by "org.netbeans.editor.Settings.PROCESSOR"
Comment 1 err 2007-07-03 01:35:44 UTC 
Created attachment 44642 [details]
Thread dump after hang
Comment 2 err 2007-07-03 01:38:58 UTC 
Created attachment 44643 [details]
messages.log after hang and forced shutdown
Comment 3 Vitezslav Stejskal 2007-07-03 10:54:42 UTC 
It should already be fixed. Could you please try a dev build?

*** This issue has been marked as a duplicate of 107400 ***