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 168411 - AWT thread blocked for 4,997 ms.
Summary: AWT thread blocked for 4,997 ms.
Status: RESOLVED WONTFIX
Alias: None
Product: ruby
Classification: Unclassified
Component: Gems (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Erno Mononen
URL: http://statistics.netbeans.org/except...
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2009-07-10 17:11 UTC by Martin Schovanek
Modified: 2009-10-08 13:50 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 153586

Attachments
nps snapshot (22.45 KB, bin/nps)
2009-07-10 17:11 UTC, Martin Schovanek 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Schovanek 2009-07-10 17:11:36 UTC 
Build: NetBeans IDE Dev (Build 200907100200)
VM: Java HotSpot(TM) Client VM, 1.5.0_19-137, Java(TM) 2 Runtime Environment, Standard Edition, 1.5.0_19-b02-304
OS: Mac OS X, 10.5.7, i386

User Comments:
mschovanek: Upgrading rspec.gem


Maximal alredy reported slowness was 4997 ms, average is 4997
Comment 1 Martin Schovanek 2009-07-10 17:11:46 UTC 
Created attachment 84606 [details]
nps snapshot
Comment 2 Erno Mononen 2009-10-08 13:50:43 UTC 
The time is spent in the list cell renderer component when refreshing the gem list (there is a lot items). This has to 
be done in AWT and the use case is not worth of implementing any complicated solutions for lazily or incrementally 
updating the list. In the code the cursor is set to busy when the operation is running, so not sure why the slowness 
detector popped up for this in the first place.