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.
This bug was originally marked as duplicate of bug 229746, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related. Build: NetBeans IDE 7.4 (Build 201310111528) VM: Java HotSpot(TM) Client VM, 23.25-b01, Java(TM) SE Runtime Environment, 1.7.0_25-b17 OS: Windows XP User Comments: GUEST: Just opening netbeans. It seems that the latest versions only get slower and slower. Please stop adding features. Start working on speed and stability in stead. Maximum slowness yet reported was 34719 ms, average is 34719
Created attachment 145335 [details] nps snapshot
this is unfortunate. AWT waits for Children.MUTEX write lock that is held by "org.netbeans.modules.project.ui.ProjectTab" running NodeOp.findPath. And that thread is stuck by accessing disk in DataObject.find - unfortunately because this is running outside of EDT, FolderChildren does not create a delayed/lazy nodes but a full node backed up by a real dataobject. So we're back in the same situation as if DataObject.find was called in AWT. Solutions could be: 1) ALWAYS create the Delayed node 2) turn off Synchronize Views with Editor - i assume that's why "org.netbeans.modules.project.ui.ProjectTab" is running 3) "org.netbeans.modules.project.ui.ProjectTab" runs NodeOp.find() in EDT *** This bug has been marked as a duplicate of bug 239779 ***