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.
A deadlock occured when editing a java souce file. More precisely, I was adding a new method to an existing class. Its trace is different from issues 164,165,242. Found one Java-level deadlock: ============================= "AWT-EventQueue-1": waiting to lock monitor 0x000dd4d0 (object 0xc663a348, a org.netbeans.modules.java.editor.semantic.OccurrencesMarkProvider), which is held by "Java Source Worker Thread" "Java Source Worker Thread": waiting to lock monitor 0x000dd5a8 (object 0xc65c2700, a org.netbeans.modules.editor.errorstripe.AnnotationViewDataImpl), which is held by "AWT-EventQueue-1" Java stack information for the threads listed above: =================================================== "AWT-EventQueue-1": at org.netbeans.modules.java.editor.semantic.OccurrencesMarkProvider.getMarks(OccurrencesMarkProvider.java:57) - waiting to lock <0xc663a348> (a org.netbeans.modules.java.editor.semantic.OccurrencesMarkProvider) ... (whole trace attached) ---- netbeans-retouche-200608050000.zip NetBeans IDE Dev (Build 060805) 1.5.0_07; Java HotSpot(TM) Client VM 1.5.0_07-b03 SunOS version 5.10 running on sparc en (nb); ISO646-US
Created attachment 34601 [details] threaddump
*** Issue 89395 has been marked as a duplicate of this issue. ***
*** Issue 90474 has been marked as a duplicate of this issue. ***
*** Issue 90578 has been marked as a duplicate of this issue. ***
Hopefully fixed: Checking in OccurrencesMarkProvider.java; /cvs/java/editor/src/org/netbeans/modules/java/editor/semantic/OccurrencesMarkProvider.java,v <-- OccurrencesMarkProvider.java new revision: 1.3; previous revision: 1.2 done