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 aug 19] I get a deadlock during the first user start (attached). After commenting out the line from PSupport.java: org.netbeans.core.AutomountSupport.initialize().waitFinished(); (which is an illegal use of core anyway BTW) the deadlock disappears (presumably something else is broken). This line was added by you in rev. 1.81 of PSupport.java on Aug 16 to fix #14493.
Created attachment 2229 [details] Deadlock thread dump
Why illegal? Module projects depends on core now. It was decided some time ago. Code has to wait for updated Registery after adding project layer to be able to deserialize winsys correctly (mainly opened files in editor). Is there a way how to reproduce the deadlock? Jarda promised to improve initialization of core.AutomountSupport.
*** Issue 14586 has been marked as a duplicate of this issue. ***
*** Issue 14607 has been marked as a duplicate of this issue. ***
Jarda, can you take a look at it? According to code in AutomountSupport.initialize returned task should be always started or scheduled but it seems that not. At least on some unix platforms.
Rewritten. Created one task that delegates to both the folder instance & the store task.
Verified.
Resolved for 3.4.x or earlier, no new info since then -> closing.