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.
[dev-200110290100; Sun JDK 1.4 beta3-b84; SDI] 1. Started with a clean userdir 2. Created a new project 'NewProject' 3. In the Project Manager, renamed the newly created (and active project) to Hello. 4. Mounted a couple of filesystems (local, jar, JavaCVS) 5. Switched to the Default project 6. Switched back to the Hello project 7. The following warnings were displayed on the console (twice) Settings saving interrupted! List of pending locks: Projects/NewProject 8. The loading of the project was interrupted, the title bar still displays Project Default. It is not possible to invoke the Project Manager anymore. 9. The UI seems to be responsive, but after a while a deadlock occurs (see attachments)
Created attachment 3186 [details] Exception stack-trace 1
Created attachment 3187 [details] Exception stack-trace 2
solving this one
Locks in SystemFileSystem are handled crrectly for renamed and deleted files now. This solved the reported problem with unsaved settings, but doesn't have any effect on dead-locks. IMO, both thread dumps show the same deadlock in vcs module's class ...vcs.advanced.CommandLineVcsFileSystemInstance. Deadlock is unreproducible in my environment: W2K, JDK 1.3.1_01 I'll try to reproduce the deadlock on JDK 1.4 beta3, if it was exposed by troubles in SystemFileSystem we could decrease prio to P2, otherwise P1 is appropriate as it prevents projects from being switched. Moving to vcscore module.
Will try to do a fix for this. Generally this is caused by creating an internal Nodes structure for the filesystem, that is used to store VCS commands. I was told, that usage of Nodes for that purpose is strange, but O.K. But this is not the first time it cause troubles. It's probably too late to change it now, I'll consider to change it to the next version (3.4 or 4.0). Preparing a workaround (less synchronized code).
Moved the work with Node(s) hierarchy outside of synchronized blocks. This should eliminate the deadlock. Please reopen if you get a deadlock like this again (I was not able to reproduce it as well on Solaris, JDK 1.4 beta3-b84). Fixed in build 10/31.
Hm, I was also not successful with the reproduction and therefore I believe it got really fixed. I am sure Jan will reopen this bug if he encounters it again. :-) Verified in development build of NetBeans 3.3 #200111010100.
Resolved for 3.4.x or earlier, no new info since then -> closing.