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 89644 - During opening new jframe nb got stacked but it's not reproducible
Summary: During opening new jframe nb got stacked but it's not reproducible
Status: VERIFIED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: Data Systems (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jaroslav Tulach
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2006-11-20 10:21 UTC by Jana Maleckova
Modified: 2008-12-22 14:58 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
89644_thread dump (23.41 KB, application/octet-stream)
2006-11-20 10:22 UTC, Jana Maleckova
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jana Maleckova 2006-11-20 10:21:08 UTC
NetBeans IDE Dev (Build 061120) M5
1.6.0-rc; Java HotSpot(TM) Client VM 1.6.0-rc-b104
Windows XP version 5.1 running on x86
cs_CZ (nb); Cp1250
dual core

Description:
============
I tried to create new jframe for several times and in one case nb got stacked.
In attachment there is thread dump, I hope it could hepl.
Comment 1 Jana Maleckova 2006-11-20 10:22:22 UTC
Created attachment 36132 [details]
89644_thread dump
Comment 2 Jana Maleckova 2006-11-22 10:10:33 UTC
It's often reproducible if you open nb with clear userdir and try to create new
appl with new jframe or jpanel
I am increasing priority because nowadays it's more common.
Comment 3 Jaroslav Tulach 2007-02-12 14:13:39 UTC
I guess you will have to attach message.log next time you see problem like 
this. As the code in CloneableEditorSupport:

throw new InterruptedException("Waiting 10s for AWT and nothing! Exiting to 
prevent deadlock"); // NOI18N

try {
  safe.waitForResult();
} catch (InterruptedException ex) {
  ERR.log(Level.INFO, null, ex);
  return false;
}

is likely good enough to prevent this kind of deadlock. Please attach the 
messages.log, the exception should be there.
Comment 4 Jana Maleckova 2007-08-20 15:20:13 UTC
now this issue doesn't happen (Build 070820)