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.
Product Version = NetBeans 5.5 Beta (Build 200605030200) Operating System = Linux version 2.6.9-1.667 running on i386 Java; VM; Vendor; Home = 1.5.0_06; Java HotSpot(TM) Client VM 1.5.0_06-b05 Try to open NB project (subversion/main - without dependencies). IDE hangs.
Created attachment 30217 [details] thread dump
This in case there are installed all modules for Subversion. In case of standard distribution of NB exceptions are thrown. See attached message.log.
Created attachment 30218 [details] message log
Hi, I think there are two different things: 1. the deadlock is caused by calling ProjectManager.findProject recursivelly - this cannot work (please see issue #60073 and issue #60011). Reassigning to subversion - see jglick's comment to issue #60011, point 1. 2. The exceptions: I do not think this has anything to do with project infrastructure: the first exception is: ava.lang.RuntimeException: DOM graph creation failed: org.netbeans.modules.schema2beans.Schema2BeansRuntimeException: Failed to create the XML-DOM Document. Check your XML to make sure it is correct. Premature end of file. at org.netbeans.modules.websvc.jaxwsmodel.project_config1_0.JaxWs.createGraph(JaxWs.java:216) =>I think this is bug in jaxwsmodel. Could you please file a bug against module?
i agree, it seems to be two different things so we should hadle it in two issues. 1. the call on xxx.cvss.FilesystemHandler.notManaged() should be done in a separate thread. actually the same way as in the event handling fix from msandor for #60011. will take care for it. 2. new issue #75910
*** Issue 75925 has been marked as a duplicate of this issue. ***
made a quick-fix in cvs so a deadlock should not appear anymore. it checks if the given file is managed by traversing the parent folder and looking for a cvs/root file. this could be quite expensive so it's still to evaluate if there is no another solution ... no deadlock so lowering the priority to p3
The code is now completely rewritten. The root cause was that CVS filesystem handler depended on the status cache in a way that could cause deadlocks. Now event handling does not query status cache at all so this issue should be fixed.
Verified.