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 171352 - AWT thread blocked for 45141 ms.
Summary: AWT thread blocked for 45141 ms.
Status: RESOLVED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Quick Search (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: David Simonek
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-02 18:56 UTC by alied
Modified: 2009-09-02 22:09 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 157669


Attachments
nps snapshot (25.94 KB, bin/nps)
2009-09-02 18:56 UTC, alied
Details

Note You need to log in before you can comment on or make changes to this bug.
Description alied 2009-09-02 18:56:09 UTC
Build: NetBeans IDE Dev (Build nbms-and-javadoc-3856-on-090902)
VM: Java HotSpot(TM) Client VM, 16.0-b03, Java(TM) SE Runtime Environment, 1.7.0-ea-b59
OS: Windows Vista, 6.0, x86

User Comments:
alied: scanning projects


Maximum slowness yet reported was 45141 ms, average is 24926
Comment 1 alied 2009-09-02 18:56:14 UTC
Created attachment 86999 [details]
nps snapshot
Comment 2 Vitezslav Stejskal 2009-09-02 21:51:12 UTC
Quick Search calls ActionsSearchProvider to find applicable actions, but loading action may generally take a long time.
I'm not sure why this is done in AWT. In the current dev build the situation is likely to be better due to fixes in
issue #170040. There is also a lot of time spent in native code when loading stuff from jar files (eg. classes and bundles).
Comment 3 David Simonek 2009-09-02 22:09:25 UTC
It's simple - a lot of actions refuse to be constructed outside of EQ thread and they are throwing assertions. Nothing I
can do on my side unfortunately. What would help is to have some way of retrieving action names quickly and without
object creation, which is not possible now AFAIK.