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.

Bug 22041 - Deadlock in CompletionJavadoc
Summary: Deadlock in CompletionJavadoc
Status: CLOSED FIXED
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P2 blocker (vote)
Assignee: issues@editor
URL:
Keywords:
: 22004 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-04-03 08:11 UTC by Petr Nejedly
Modified: 2007-11-05 13:44 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Stack trace of AWT-EventQueue and OpenIDE-request-processor-0 (5.16 KB, text/plain)
2002-04-03 08:14 UTC, Petr Nejedly
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Nejedly 2002-04-03 08:11:59 UTC
CompletionJavaDoc is changing the visibility
of its components from inside of non-AWT thread,
which can cause deadlock.
Will attached stacktrace.
Comment 1 Petr Nejedly 2002-04-03 08:14:26 UTC
Created attachment 5266 [details]
Stack trace of AWT-EventQueue and OpenIDE-request-processor-0
Comment 2 Martin Roskanin 2002-04-04 16:16:03 UTC
*** Issue 22004 has been marked as a duplicate of this issue. ***
Comment 3 Martin Roskanin 2002-04-05 07:13:32 UTC
fixed in [maintrunk]

/cvs/editor/libsrc/org/netbeans/editor/ext/CompletionJavaDoc.java,v  
<--  CompletionJavaDoc.java
new revision: 1.3; previous revision: 1.2
Comment 4 Jan Lahoda 2002-04-05 13:34:43 UTC
Probably can only happen while doing external reload of a file.
Comment 5 Petr Nejedly 2002-04-08 08:20:16 UTC
Yes, it have happened during document reload, but
No, it could happen anytime when something is changing the document
from out of AWT thread and changing document from other threads
shall work OK.
Comment 6 Quality Engineering 2003-06-30 18:14:53 UTC
Resolved for 3.3.x or earlier, no new info since then -> closing.