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 IDE Dev (Build 200301060100) IDE Versioning = IDE/1 spec=3.26 impl=200301060100 Operating System = Linux version 2.4.18 running on i386 Java; VM; Vendor = 1.4.1_01; Java HotSpot(TM) Client VM 1.4.1_01-b01; Sun Microsystems Inc. Java Home = /usr/java/j2sdk1.4/sun/jdk1.4.1_01/jre System Locale; Encod. = cs_CZ; ISO-8859-2 Home Dir; Current Dir = /home.local/danielm; /DISKS/storage3/forte/NBdev-last/netbeans/bin IDE Install; User Dir = /home.local/danielm/NBdev-last; /home.local/danielm/.netbeans/dev ------------------------------------------------------------------------------- I have mounted G-CVS with specified relative mountpoint. I deleted content of the realtivemountpoint aoutside of ide. Then I started ide. On the FS I perform checkout module... Then after a while (after module was checkouted)...probalby started Refreshing statuses....and in this time my ide died:-( See the attached FTD,please
Created attachment 8456 [details] Full Thread Dump
Not easily solvable in the current design. The problem seems to be in "VCS Status Update Request Processor" stack trace. VcsAttributes search for the FileObject reference, which should be avoided (at org.netbeans.modules.vcscore.VcsAttributes.readAttribute(VcsAttributes.java:246))
This deadlock can be also avoided if VcsVersioningFileSystem.vcsStatusChanged() is processed asynchronously in analogy to VcsFileSystem.statusChanged().
This DEADLOCK is easyly reproductable:-( by checkin' out 'vcsgeneric' module (while you have set RMP to src package)
This deadlock should be fixed in the main trunk. It collects the files and performs the status update in a separate thread. /cvs/vcscore/src/org/netbeans/modules/vcscore/VcsVersioningSystem.java,v <-- VcsVersioningSystem.java new revision: 1.33; previous revision: 1.32 However there is still a potential deadlock in VcsAttributes, which might not happen at all depending on what other threads will be doing. I'll file a task for that problem.
FYI: task #29845 was submitted for the problem in VcsAttributes.
Well done Martin, I can't reproduce it with my testcase on build #2003-0109-0100 ;-)
reopen to fix status and resolution
fix status and resolution
good work;-) thx 4 tha fix