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 172321 - AWT thread blocked for 40250 ms.
Summary: AWT thread blocked for 40250 ms.
Status: RESOLVED DUPLICATE of bug 173109
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jesse Glick
URL: http://statistics.netbeans.org/except...
Keywords: PERFORMANCE
Depends on:
Blocks: 173109
  Show dependency tree
 
Reported: 2009-09-15 18:41 UTC by Jan Lahoda
Modified: 2010-02-04 13:45 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 158551


Attachments
nps snapshot (48.54 KB, bin/nps)
2009-09-15 18:41 UTC, Jan Lahoda
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Lahoda 2009-09-15 18:41:31 UTC
Build: NetBeans IDE Dev (Build jet-main-1201-on-090908)
VM: Java HotSpot(TM) Client VM, 11.0-b16, Java(TM) SE Runtime Environment, 1.6.0_11-b03
OS: Linux, 2.6.28-11-generic, i386
Maximum slowness yet reported was 40250 ms, average is 40250
Comment 1 Jan Lahoda 2009-09-15 18:41:56 UTC
Created attachment 87715 [details]
nps snapshot
Comment 2 rmichalsky 2009-09-29 15:34:06 UTC
Stack Analyzer probably really needs all registered source roots, thus full module list scan is IMHO necessary in this
case and I don't see any potential significant speed up in apisupport. I guess Stack Analyzer could do the navigation in
background. CC-ing Honza Becicka, as he seems to be the original author of Stack Analyzer, don't know if he still
maintains it.
Comment 3 Jesse Glick 2009-09-29 15:36:33 UTC
Check my snapshot. I do not think I even have stackanalyzer installed (whatever it is).
Comment 4 rmichalsky 2009-09-29 19:51:28 UTC
I see, your snapshot is quite different, I wonder why has it been marked as duplicate. In this case full module scan is
quite needless, will be resolved with issue #173109.
Comment 5 Jesse Glick 2010-02-04 13:45:49 UTC

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