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 193899 - NB deadlock when entering JavaDoc comment
Summary: NB deadlock when entering JavaDoc comment
Status: RESOLVED DUPLICATE of bug 194045
Alias: None
Product: versioncontrol
Classification: Unclassified
Component: Code (show other bugs)
Version: 7.0
Hardware: PC Linux
: P3 normal (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-29 05:19 UTC by rcasha
Modified: 2011-10-18 10:28 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Heap dump + last few lines on console. (18.23 KB, text/plain)
2010-12-29 05:19 UTC, rcasha 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description rcasha 2010-12-29 05:19:42 UTC 
Created attachment 104580 [details]
Heap dump + last few lines on console.

I was typing in the JavaDoc comments and had just entered "{@link " - the popup menu listing @code, @docRoot etc was still visible, and NB got stuck there. Nothing is responsive, and the "graph" of memory usage is also stopped.


Product Version: NetBeans IDE Dev (Build nbms-and-javadoc-6381-on-101224)
Java: 1.7.0-ea; Java HotSpot(TM) Client VM 20.0-b03
System: Linux version 2.6.32-27-generic running on i386; UTF-8; en_US (nb)



Note that this version is more recent than the last build in the nightly, so the original problem with JDK1.7 should have been resolved.
Comment 1 Svata Dedic 2011-10-18 10:20:57 UTC 
Caused by version control - do not call repaint in (potentially) non-AWT thread from foldHierarchyChanged. RepaintManager tries to acquire the AWT tree lock.
Comment 2 Ondrej Vrabec 2011-10-18 10:28:31 UTC 

*** This bug has been marked as a duplicate of bug 194045 ***