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 140576 - Profiler blocks startup
Summary: Profiler blocks startup
Status: RESOLVED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: J Bachorik
URL:
Keywords:
: 140575 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-07-17 16:06 UTC by Jaroslav Tulach
Modified: 2011-10-03 12:55 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread dump showing the profiler initialization (3.02 KB, text/plain)
2008-07-17 16:07 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 2008-07-17 16:06:08 UTC 
Can you modify profiler to not do anything on startup until the user really invokes one of the profiler actions? At 
least do not start any own threads, do not load settings, possibly use org.openide.Actions.alwaysEnabled XML layer 
declaration to prevent actions from your module being loaded, please remove your ModuleInstall and do the 
initialization lazily when needed, etc.

I am attaching one stack trace that I got on startup which shows that the start time is wasted in initialization of 
ProfilerManager. Please eliminate this initialization.
Comment 1 Jaroslav Tulach 2008-07-17 16:07:35 UTC 
Created attachment 64872 [details]
Thread dump showing the profiler initialization
Comment 2 Tomas Hurka 2008-07-18 10:50:09 UTC 
*** Issue 140575 has been marked as a duplicate of this issue. ***
Comment 3 Jiri Sedlacek 2008-08-01 13:08:00 UTC 
Will try to at least improve it a bit for 6.5.
Comment 4 J Bachorik 2009-04-27 16:04:35 UTC 
Will need a more thorough redesign of the profiler infrastructure. Definitely it's too late to introduce such a change
now. Hopefully, there will be some time to be spent on this in the next release.
Comment 5 J Bachorik 2011-10-03 12:55:48 UTC 
This seems to have been resolved during the process of profiler modularization (preparation for NetBeans/JDev common profiler)