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 176753 - AWT thread blocked for 30141 ms.
Summary: AWT thread blocked for 30141 ms.
Status: RESOLVED WORKSFORME
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: issues@guibuilder
URL:
Keywords: PERFORMANCE
: 239009 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-11-13 00:36 UTC by Exceptions Reporter
Modified: 2013-12-02 10:38 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 161996


Attachments
nps snapshot (256.00 KB, application/nps)
2009-11-13 00:36 UTC, Exceptions Reporter
Details
nps snapshot (256.00 KB, application/nps)
2009-11-30 08:35 UTC, hedefalk
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2009-11-13 00:36:26 UTC
Build: NetBeans IDE 6.8 Beta (Build 200910212001)
VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01
OS: Windows XP, 5.1, x86
Maximum slowness yet reported was 30141 ms, average is 30141
Comment 1 Exceptions Reporter 2009-11-13 00:36:30 UTC
Created attachment 90973 [details]
nps snapshot
Comment 2 Jan Stola 2009-11-13 02:11:48 UTC
AWT thread is blocked by some ugly sleep() calls introduced as a workaround of issue 101719. The issue 101719 is claimed to be fixed by now. Hence, the fix of issue 101719 is not correct or there is another reason why the generated entity do not appear in the model (for example, it can happen when the generation of the entity fails without throwing an exception). I need reproducible steps to be able to evaluate this issue. Unfortunately, there is nobody to ask for such steps (this issue is anonymous) => closing as non-reproducible.
Comment 3 hedefalk 2009-11-30 08:35:19 UTC
Created attachment 91868 [details]
nps snapshot
Comment 4 Tomas Pavek 2013-12-02 10:38:05 UTC
*** Bug 239009 has been marked as a duplicate of this bug. ***