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.
Created attachment 127163 [details] Thread Dump Product Version: NetBeans IDE Dev (Build 201210310001) Updates: Updates available Java: 1.6.0_33; Java HotSpot(TM) 64-Bit Server VM 20.8-b03
at org.openide.util.Mutex.isReadAccess(Mutex.java:509) - locked <0x00000000d11a0fa8> (a org.openide.util.Mutex$InternalLock) at org.openide.util.Mutex.isReadAccess(Mutex.java:503)
Two threads are fighting repeatedly for the Mutex, org.netbeans.modules.project.ui.ProjectTab and AWT-EventQueue-1. This is not a real deadlock (only one of the two threads is BLOCKED at a time), but starvation caused by the repeated attempts to acquire the mutex and then wait in both threads as they go node by node through a long list of nodes. The culprit is the code at at org.openide.util.Mutex.isReadAccess(Mutex.java:509) - locked <0x00000000d11a0fa8> (a org.openide.util.Mutex$InternalLock) at org.openide.util.Mutex.isReadAccess(Mutex.java:503) at org.openide.loaders.FolderChildren.checkChildrenMutex(FolderChildren.java:317) at org.openide.loaders.FolderChildren.getNodes(FolderChildren.java:269) If a list of nodes is very long, this back and forth between the two threads can take very long and seem like a deadlock. -> platform / nodes
See also issue 221279 which is a result of the same root cause.
*** This bug has been marked as a duplicate of bug 221279 ***