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 240436 - org.openide.explorer.view.TreeView$ExplorerTree.<init>: LowPerformance took 31499 ms.
Summary: org.openide.explorer.view.TreeView$ExplorerTree.<init>: LowPerformance took 3...
Status: RESOLVED WONTFIX
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Infrastructure (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Milos Kleint
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2014-01-14 03:49 UTC by darrenoh
Modified: 2014-01-15 07:41 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 174163

Attachments
nps snapshot (91.70 KB, application/nps)
2014-01-14 03:49 UTC, darrenoh 		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 darrenoh 2014-01-14 03:49:11 UTC 
Build: NetBeans IDE 7.4 (Build 201310111528)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.7-b01, Java(TM) SE Runtime Environment, 1.7.0_17-b02
OS: Mac OS X

User Comments:
GUEST: Opened the program

GUEST: Just launch IDE

darrenoh: I had forced NetBeans to close because it was not responding. Two projects were open. Then I started NetBeans again.



Maximum slowness yet reported was 31499 ms, average is 11087
Comment 1 darrenoh 2014-01-14 03:49:13 UTC 
Created attachment 143928 [details]
nps snapshot
Comment 2 Ondrej Vrabec 2014-01-14 09:23:08 UTC 
AWT is busy with class-loading which is most likely slowed down by running "Load Open Projects" thread. Cannot be fixed in explorer, passing to projects. Maybe there's a chance to delay project opening until the UI is fully ready? Or maybe a wontfix, i leave it up to projects.
Comment 3 Milos Kleint 2014-01-15 07:41:09 UTC 
there's significantly more bottlenecks than just loadClass in the 2 most recent snapshots.

What I believe is important is that 1.7 build preceding the 21 update are used, I've seen way too many reports that used these old jdk builds that stopped appearing with never jdk updates. I believe this is a similar case. A concurrent load from other applications could also play a role, but such snapshots look a bit different though.

Please update to latest jdk.