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 189849 - IDE freezes when trying to open a Swing form in design view
Summary: IDE freezes when trying to open a Swing form in design view
Status: RESOLVED DUPLICATE of bug 187697
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P1 normal (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-25 14:01 UTC by roger_rf
Modified: 2010-08-27 10:04 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Thread Dump showing deadlock (19.46 KB, text/plain)
2010-08-25 14:01 UTC, roger_rf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description roger_rf 2010-08-25 14:01:44 UTC
Created attachment 101661 [details]
Thread Dump showing deadlock

For a few days now, I've been facing a rather annoying problem: I choose a Swing form (JFrame, JDialog, JPanel) in the Projects tab, and then I open it using the "Edit" menu. After looking at the source code of the form for a bit, I click the "Design" button to have a look at the GUI. The form never loads, as the IDE freezes completely. This seems to be completely random, I can't find a way to reliably reproduce it.

I tried monitoring NB using JVisualVM and saved a thread dump after the IDE froze, JVisualVM identified a deadlock. The thread dump is attached to this report. I also saved a heap dump, but I don't know if I should attach it, since it's way too big (~86 MB uncompreesed, ~19.5 MB compressed) and I don't know if it's relevant to diagnose this problem. My setup is as follows:

Product Version: NetBeans IDE 6.9.1 (Build 201007282301)
Java: 1.6.0_21; Java HotSpot(TM) Client VM 17.0-b17
System: Windows XP version 5.1 running on x86; Cp1252; en_BR (nb)
Comment 1 Jan Stola 2010-08-27 10:04:48 UTC

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