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.
Summary: | Profiler slows down IDE startup | ||
---|---|---|---|
Product: | profiler | Reporter: | Oleg Khokhlov <ovk> |
Component: | Base | Assignee: | Tomas Hurka <thurka> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | issues |
Priority: | P2 | Keywords: | VISUALVM |
Version: | 6.x | ||
Hardware: | All | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Oleg Khokhlov
2009-08-07 11:59:09 UTC
I am unable to reproduce it. I used after cold startup with existing userdir. See the log below: Product Version: NetBeans IDE Dev (Build 200910151401) Java: 1.7.0-ea; Java HotSpot(TM) Client VM 16.0-b06 System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb) Userdir: C:\Documents and Settings\Administrator\.netbeans\dev @5941 - ModuleInstall for org.netbeans.modules.profiler.selector.spi/1 called dT=0 @5942 - ModuleInstall for org.netbeans.modules.profiler.selector.ui/1 called dT=1 @6166 - ModuleInstall for org.netbeans.modules.profiler/1 called dT=224 @6166 - ModuleInstall for org.netbeans.modules.profiler.j2ee.sunas/1 called dT=0 @6166 - ModuleInstall for org.netbeans.libs.cglib/1 called dT=0 I will try different machine. Can't you eliminate all work done in org.netbeans.modules.profiler/1? If the ModuleInstall is empty, then it does not matter how bad configuration of a computer is used to execute it. I removed profiler initialization from restore() method. I would still like to know how you have got 23 seconds long initialization with the original code. changeset: 152580:7a58d1f39b0b user: Tomas Hurka <thurka@netbeans.org> date: Wed Nov 11 13:35:02 2009 +0100 summary: bugfix #170036, Profiler.getDefault() removed from restore(); profiler is initilaized lazily later |