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 150127 - org.netbeans.modules.profiler classes are loaded during NetBeans startup with LimeWire project
Summary: org.netbeans.modules.profiler classes are loaded during NetBeans startup with...
Status: RESOLVED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: issues@profiler
URL: http://wiki.netbeans.org/FitnessViaWh...
Keywords: PERFORMANCE, TEST
Depends on:
Blocks:
 
Reported: 2008-10-14 18:43 UTC by Alexander Kouznetsov
Modified: 2009-03-23 16:21 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Stacktraces (10.76 KB, text/plain)
2008-10-14 18:43 UTC, Alexander Kouznetsov 		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 Alexander Kouznetsov 2008-10-14 18:43:21 UTC 
Performance whitelist test reports that following classes are loaded during NetBeans startup with LimeWire project:

org.netbeans.modules.profiler.j2se.LookupProviderImpl
org.netbeans.modules.profiler.nbmodule.LookupProviderImpl
org.netbeans.modules.profiler.projectsupport.AbstractProjectLookupProvider

Please don't load these classes unless they are really necessary. More information about the test available via the URL
specified.

Comment from jtulach: 
A bug in profiler that can potentially need enhancements in project 
infrastructure. We need a way to declaratively register lookup enhancements. 
Maybe a similar bug for profiler has already been reported and discussed?

Comment from yardus:
Yes. There was a similar bug
http://www.netbeans.org/issues/show_bug.cgi?id=142764
The problem is that there is no way to register an additional project
lookup and not to cause startup regression in class loading. Once you
register an additional project lookup it's class (and superclasses) must
be all loaded once the project is accessed.

Comment from mrkam:
That issue is already fixed while this is still reproducible. So the issue is filed.
Comment 1 Alexander Kouznetsov 2008-10-14 18:43:46 UTC 
Created attachment 71792 [details]
Stacktraces
Comment 2 J Bachorik 2008-10-15 10:39:09 UTC 
This seems to be more project related problem
not for 6.5
Comment 3 Jesse Glick 2009-01-22 02:16:16 UTC 
Issue #150194 is unlikely to be useful here, as the Profiler modules use rather complicated LookupProvider impls which
do not look possible to refactor into a form that @ProjectServiceProvider could be applied to. You can probably make
your LP impls lazier, but avoiding loads of the abovementioned classes is probably not possible.
Comment 4 J Bachorik 2009-03-23 16:21:20 UTC 
This should be fixed as the LookupProvider was replaced by @ProjectServiceProvider thus allowing for bigger laziness.