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 build from 1-Apr-2003, JDK 1.4.1_02] I was switching editor tabs and attempting to edit a file when I got what appears to be a deadlock. I was also making a file read-write (from read-only) at about the same time. I can't reproduce this, but I do have the stack trace, which I'll attach.
Created attachment 9675 [details] stack dump
Reassigning to openide/text ... AWT thread is waiting for task.finished in "Default RequestProcessor" and "Default RequestProcessor" is waiting for the lock 0458B3E0 which has been taken firstly in AWT thread.
It should be fixed in Nb35.
> It should be fixed in Nb35. at this stage of the cycle we are fixing only showstoppers. Is this a showstopper? jrichardson said he cannot reproduce the bug. I am always nervous whenever we are changing anything related to thread/locking
Without reproducible case I do not dare to fix it in NB35 nor in the trunk. The code in text package related to loading of document and document lines is known to be buggy and must be refactored/rewritten. Fixing anything in current state is quite dangerous. So, TM=future. I'm intentionally lowering priority to P3. If this problem happens again please mention it here. Based on the frequency we can increase priority back to P2 and try to solve it.
Created attachment 9684 [details] excerpt from the dump with two dead threads.
I agree with David's solution. It's really dangerous fix this type of issues now.
Deadlock has the same symptom as in issue 33062. *** This issue has been marked as a duplicate of 33062 ***
verified, closed - it's duplicate.