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 198906 - Deadlock on loading form for GUI Builder
Summary: Deadlock on loading form for GUI Builder
Status: RESOLVED DUPLICATE of bug 187697
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 7.0
Hardware: PC Windows XP x64
: P3 normal (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-26 09:50 UTC by marcodave
Modified: 2011-05-26 11:59 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
thread dump from VisualVM (24.72 KB, text/plain)
2011-05-26 09:51 UTC, marcodave 		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 marcodave 2011-05-26 09:50:35 UTC 
I was trying to load a form in the matisse gui builder.
Netbeans stopped responding to GUI events.
I made a thread dump with VisualVM. 
In the dump seems like the "AWT-EventQueue-1" thread has 
at java.beans.Introspector.getBeanInfo(Introspector.java:157)
 - waiting to lock <0x000000001d7715f0> (a java.lang.Object)
....
 - locked <0x0000000006003328> (a java.lang.Class for java.beans.Introspector)


and "GUI Builder" has
at java.beans.Introspector.findExplicitBeanInfo(Introspector.java:426)
 - waiting to lock <0x0000000006003328> (a java.lang.Class for java.beans.Introspector)
at java.beans.Introspector.<init>(Introspector.java:377)
at java.beans.Introspector.getBeanInfo(Introspector.java:164)
 - locked <0x000000001d7715f0> (a java.lang.Object)

Seems like a bad deadlock to me.
Comment 1 marcodave 2011-05-26 09:51:31 UTC 
Created attachment 108519 [details]
thread dump from VisualVM
Comment 2 marcodave 2011-05-26 10:16:28 UTC 
seems that disabling the spellchecker solves the problem for now (not that I needed the spellchecker).
It's a dirty workaround, though, I hope that someone solves the bug.
Comment 3 Jan Stola 2011-05-26 11:59:08 UTC 
It is caused by JDK bug (that was resolved in the latest JDK builds).

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