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.
| Summary: | Deadlock between lib.editor and AWT tree lock | ||
|---|---|---|---|
| Product: | editor | Reporter: | Jaroslav Tulach <jtulach> |
| Component: | -- Other -- | Assignee: | issues@editor <issues> |
| Status: | VERIFIED FIXED | ||
| Severity: | blocker | CC: | blaha, mslama, sustaining |
| Priority: | P2 | Keywords: | RANDOM, THREAD |
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: | Thread dump | ||
|
Description
Jaroslav Tulach
2009-06-23 10:06:15 UTC
Created attachment 83914 [details]
Thread dump
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) Changeset: http://hg.netbeans.org/main-golden/rev/768ba6b2684c User: Miloslav Metelka <mmetelka@netbeans.org> 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. http://hg.netbeans.org/release67_fixes/rev/7b39373256c0 v in 6.5.1 |