Not the first time I struggled over a deadlock which appears when I close the project properties dialog after adding a
project dependency to a module project from a suite. I have attached a stacktrace for this deadlock in NB RC2. But I
also noticed it in other daily builds.
Created attachment 60542 [details]
Thread dump fro the deadlock
Happened just again, the 3rd time today, after modifying the list of public packages. I'll attach a thread dump.
Created attachment 60548 [details]
Another thread dump for the deadlock
Probably fixed in #a38a9a3078c0 which I will push to core-main.
Any chance to find the fix in the final 6.1?
Too late for 6.1. Could go into some patch release, but I am not involved in that decision. If the deadlock is frequent
or reproducible, feel free to mark as a P2, which will improve the chances of it being noticed as a candidate for a
patch. Of course if you can verify the fix in a dev build, that would be very helpful.
Issue '133639' Integrated in NB_Trunk_Production #154 : http://hg.netbeans.org/main/rev/a38a9a3078c0,
with comment: #133639: deadlock after modifying project properties.
I will increase priority to P2 to improve the chance to get this issue being noticed as a candidate for a
patch: in 1 of 2 cases I can reproduce the deadlock on closing the module property dialog. This is more than annoying
particularly when I had unsaved files. Yesterday this issue caused me to kill and restart NB 4 times. So I started to
work around this issue by manually modifying dependencies and public packages in project.xml.
Again, if the reporter is able to verify the fix (e.g. trunk build with fix does not display deadlock under similar
conditions after at least ten attempts), that would be helpful.
just for information, the trunk build is available here: http://bits.netbeans.org/dev/nightly/latest/
I have tested the latest build from trunk (200804250004) and the problem seems to be fixed. Feel free to mark the issue
Great, thank you!
*** Issue 134177 has been marked as a duplicate of this issue. ***
IMHO candidate for 6.1 patch2
*** Issue 134486 has been marked as a duplicate of this issue. ***
The fix has been ported into the release61_fixes branch:
*** Issue 135636 has been marked as a duplicate of this issue. ***