While working on issue 166192 and opening a webmaven project from command line I have noticed a deadlock.
Created attachment 83914 [details]
The "AWT-EventQueue-1" thread acquires the AWTTreeLock and then tries to acquire the LockView's PriorityMutex and ends
up waiting. The "FoD Warm Up" thread first acquires the PriorityMutext in JavaEditorWarmUpTask and then tries to acquire
the AWTTreeLock, which obviously leads to a deadlock. IMO we should somehow fix the JavaEditorWarmUpTask.
Integrated into 'main-golden', will be available in build *200906240201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Miloslav Metelka <email@example.com>
Log: #167518 - Deadlock between lib.editor and AWT tree lock.
Jardo, would you verify the fix in the latest trunk build? Thanks. We will include the fix in patch1.
Verified in 200907070200
The fix has been ported into the release67_fixes repository.
v in 6.5.1