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.
I got deadlock during switching WS. I exited IDE in Debugging WS and then started again. Deadlock occured after switching from Debugging WS to another (Editing). The deadlock occured when editor window came up. I can provide userdir, because it seems reproducible.
Created attachment 4492 [details] full thread dump
CCing Yarda to propose, how to fix this deadlock. Should deserialization run in separate thread or the read data should be instantiated later? It isn't reproducible, however it can happen under normally circumstances. Fix will not be trivial. From these reasons this will not go into 3.3.1.
FolderChildren calls waitFinished() on default Request Processor. Jarda, could FolderChildren use its private request processor?
Created attachment 4617 [details] Should not this be fixed in ExplorerManager - the code used to be there, but was commented out for some reason
The deadlock also occurs when executing, if execution is set to swith to workspace running. I've not been able reproduce it, but it happens quite frequently, several times every day. Since I changed execution- setting NOT to swith, it has never happened. (Running nb 3.3.1 on winnt sp 6)
Jesse, as cvs annotate shows, you commented out posting of initialization into request processor. Now it seems that we have troubles with it (look at deadloceked stack traces) Can you explain why you did it and if I can revert it? 1.19 (jglick 25-Apr-00):
1.19 did not do it, that was reindenting for open source - check the log. The code in question was added in 1.11 by Yarda :-) and the RequestProcessor line was commented out from the start, it seems.
Looks I was playing with RP and then decided to invoke the code directly. Probably ok to move to RP...
ok, I'll try it :-)
committed into main trunk.
Risky fix. Will not be fixed for FFJ 4.0 (Orion).
Waiver approved.
Cannot reproduce.
Resolved for 3.4.x or earlier, no new info since then -> closing.
This issue had *1 votes* before move to platform component