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.
Reported by a user with a custom build of 20050111 sources: "I checked out the netbeans trunk this afternoon, installed some extra modules, ran it and ran into the below deadlock (which looks like they're in standard code)." Found one Java-level deadlock: ============================= "Refresh-After-WindowActivated": waiting to lock monitor 0x180d36c (object 0x7492ca0, a org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObjectFactory), which is held by "AWT-EventQueue-1" "AWT-EventQueue-1": waiting to lock monitor 0x180d2dc (object 0x74989d0, a java.util.Collections$SynchronizedMap), which is held by "Refresh-After-WindowActivated" Java stack information for the threads listed above: =================================================== "Refresh-After-WindowActivated": at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObjectFactory.get(FileObjectFactory.java:121) - waiting to lock <0x7492ca0> (a org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObjectFactory) at org.netbeans.modules.masterfs.filebasedfs.fileobjects.BaseFileObj.getExistingParent(BaseFileObj.java:302) at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObjectFactory.refreshAll(FileObjectFactory.java:60) - locked <0x74989d0> (a java.util.Collections$SynchronizedMap) ... Full stack trace attached.
Created attachment 19631 [details] Thread dump
Fixed in trunk. /cvs/openide/masterfs/src/org/netbeans/modules/masterfs/filebasedfs/fileobjects/FileObjectFactory.java new revision: 1.4; previous revision: 1.3
Verified.