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 142764 - Startup regression: org.netbeans.modules.profiler
Summary: Startup regression: org.netbeans.modules.profiler
Status: CLOSED FIXED
Alias: None
Product: ide
Classification: Unclassified
Component: Performance (show other bugs)
Version: 3.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jaroslav Tulach
URL: http://wiki.netbeans.org/FitnessViaWh...
Keywords: PERFORMANCE, REGRESSION, TEST
Depends on:
Blocks:
 
Reported: 2008-08-04 09:49 UTC by Alexander Kouznetsov
Modified: 2011-05-25 11:38 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Stacktraces (32.07 KB, text/plain)
2008-08-04 09:50 UTC, Alexander Kouznetsov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kouznetsov 2008-08-04 09:49:39 UTC
Performance test reports there is a NetBeans startup regression which is caused by the loading of the following classes:

org.netbeans.modules.profiler.categories.Categorization
org.netbeans.modules.profiler.categories.Category
org.netbeans.modules.profiler.categories.CategoryBuilder
org.netbeans.modules.profiler.categories.CategoryContainer
org.netbeans.modules.profiler.nbmodule.LookupProviderImpl
org.netbeans.modules.profiler.projectsupport.AbstractProjectLookupProvider
org.netbeans.modules.profiler.utilities.Visitable
org.netbeans.modules.profiler.utilities.Visitor

Please don't load these classes during NetBeans startup.

Comment from jtulach: "Bug. Let them explain what they do."

Regression occurred between 07/15/2008 and 07/28/2008.
Comment 1 Alexander Kouznetsov 2008-08-04 09:50:31 UTC
Created attachment 66452 [details]
Stacktraces
Comment 2 J Bachorik 2008-08-04 10:35:06 UTC
We have a new LookupProvider registered for various project types. This provider creates a lookup of services related to
profiling categorization. It's supposed to be loaded lazily when a project is being requested. The problem is that such
a project is being requested during startup - the stacktraces provided show that the problem originates in the mercurial
module. Thus reassigning there for re-evaluation.
Comment 3 Maros Sandor 2008-08-04 12:25:30 UTC
Mercurial code runs during file operations that involve files managed by mercurial. This is of course intentional. Are
tests run in the environment that contains mercurial-managed files? If so, I suggest you change testing environment or
add the new provider classes to whitelist.
Comment 4 Alexander Kouznetsov 2008-08-05 13:02:29 UTC
Tests are run without any projects opened. Is it enough for the environment to be free from mercurial-managed files?
Comment 5 Jaroslav Tulach 2008-09-02 14:57:31 UTC
I think I fixed this issue, hopefully together with many similar ones. Now the mercurial ignores the $nb_all/.hg. As 
such our whitelist shall get smaller, because a lot of project related infrastructure will not be initialized.

changeset:   99220:aeab5d4012e6
tag:         tip
user:        Jaroslav Tulach <jtulach@netbeans.org>
date:        Tue Sep 02 15:54:56 2008 +0200
summary:     #142764: A little bit of reflection helps to convince the Hg plugin that user dir is not versioned

Comment 6 Quality Engineering 2008-09-04 06:11:20 UTC
Integrated into 'main-golden', will be available in build *200809040201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/aeab5d4012e6
User: Jaroslav Tulach <jtulach@netbeans.org>
Log: #142764: A little bit of reflection helps to convince the Hg plugin that user dir is not versioned
Comment 7 Alexander Kouznetsov 2008-10-13 11:17:03 UTC
Verified with 081011