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 179070 - AWT thread blocked for 24606 ms.
Summary: AWT thread blocked for 24606 ms.
Status: NEW
Alias: None
Product: obsolete
Classification: Unclassified
Component: Embedded Mozilla (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Stanislav Aubrecht
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2009-12-28 05:12 UTC by Exceptions Reporter
Modified: 2013-05-07 10:04 UTC (History)
70 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 163955


Attachments
nps snapshot (256.00 KB, application/nps)
2009-12-28 05:12 UTC, Exceptions Reporter
Details
nps snapshot (256.00 KB, application/nps)
2010-01-08 08:56 UTC, Exceptions Reporter
Details
nps snapshot (256.00 KB, application/nps)
2010-01-13 11:21 UTC, ivanqueiroz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2009-12-28 05:12:25 UTC
Build: NetBeans IDE 6.8 (Build 200912041610)
VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01
OS: Windows 7, 6.1, x86
Maximum slowness yet reported was 24606 ms, average is 24606
Comment 1 Exceptions Reporter 2009-12-28 05:12:29 UTC
Created attachment 92954 [details]
nps snapshot
Comment 2 Exceptions Reporter 2010-01-08 08:56:02 UTC
Created attachment 93137 [details]
nps snapshot
Comment 3 ivanqueiroz 2010-01-13 11:21:11 UTC
Created attachment 93259 [details]
nps snapshot
Comment 4 Marian Petras 2010-05-14 08:49:57 UTC
From the comments added by reporters, it seems there are two suspicious actions:
- opening Web project
- opening CSS files

Note that there are 83 duplicate reports of the slowness.

I looked at the last snapshot (part of report #387136) and found the following:
 - when the editor gets focus, editor bookmarks start loading (in the AWT thread)
    - this includes loading the project's configuration file and validation
    - this action itself took about 1566 ms in my case
 - when the editor gets focus, the WebPreviewTopComponent is being loaded (in AWT)
    - initialization of the WebPreviewTopComponent took about 5124 ms in my case
       - this is a way too long

I have the Web Preview plugin installed but I do not remember using it yet. I am almost sure that I did not have the web preview TopComponent open at the time I was closing the IDE.

Note that there are many NPS snapshots available in the slowness reports so you have lot of data to use.
Comment 5 Marian Petras 2010-05-14 08:55:46 UTC
The many slowness reports imply that the embedded browser is the main suspect - reassigning to the corresponding product/component (platform / Embedded Browser).
Comment 6 muellermi 2011-06-24 08:16:34 UTC
This morning, starting the ide for the first caused lots of "slowness detected", up to 25 s.
a) during "scanning projects" phase
b) whilst reporting this issue
After log off and on again, starting for the second time, I had less slowness and had been happy to get my system to work
According to Martin Fousek, I switched bak to JDK 1.6 B 25, and got this trouble again, but only apx. 4 s each
Comment 7 spao001 2012-09-04 07:03:26 UTC
"Scanning project" delays startup of netbeans