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 186706 - 9s - right click on project popup
Summary: 9s - right click on project popup
Status: RESOLVED WONTFIX
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Infrastructure (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Jesse Glick
URL:
Keywords: PERFORMANCE
: 187861 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-05-26 06:49 UTC by Jaroslav Tulach
Modified: 2010-06-21 17:48 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 170127

Attachments
nps snapshot (29.83 KB, application/nps)
2010-05-26 06:50 UTC, Jaroslav Tulach 		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 Jaroslav Tulach 2010-05-26 06:49:58 UTC 
This bug was originally marked as duplicate of bug 176442, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE Dev (Build 100511-5b0ca7653b2c)
VM: OpenJDK Client VM, 14.0-b16, OpenJDK Runtime Environment, 1.6.0_18-b18
OS: Linux

User Comments:
jtulach: I right clicked on popup of JavaSE project node in projects tab. I found 9s of inactivity very annoying.



Maximum slowness yet reported was 9312 ms, average is 9312
Comment 1 Jaroslav Tulach 2010-05-26 06:50:02 UTC 
Created attachment 99472 [details]
nps snapshot
Comment 2 Jesse Glick 2010-05-26 13:54:06 UTC 
Mostly in template preparation, which we already try to warm up when the project is opened; ultimately largely in lookup. A bit more creating other miscellaneous actions, just class loading. Looks like Kenai login was running in another thread and probably grabbing a lot of the CPU and disk bandwidth. I don't see any targets for optimization.
Comment 3 Jesse Glick 2010-06-21 17:48:08 UTC 
*** Bug 187861 has been marked as a duplicate of this bug. ***