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 69219 - Profiling on NBM project does not work
Summary: Profiling on NBM project does not work
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: All Windows ME/2000
: P2 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-23 23:40 UTC by Rich Unger
Modified: 2007-02-20 18:09 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rich Unger 2005-11-23 23:40:12 UTC
Created a simple nbm project (either in a suite or standalone) with one class. 
The class is a CookieAction which I added to my layer in Loaders/text/html/Actions.

Selected "Profile Project", then "Analyze Performance", then "Part of
Application", and selected the action's performAction() method as my root, with
a filter of "Exclude Java Core Classes".

When I run the profiler and right-click an html file, a popup window tells me
that it's instrumenting my bytecode.  When it finishes, I run my CookieAction. 
No results are computed in Live Results.

I also can't do heap profiling.  Only thread profiling seems to give me any results.
Comment 1 Rich Unger 2005-11-23 23:42:20 UTC
By the way, I ran the profiler tutorial with its example projects, and they
returned valid results.  It seems to be just nbm projects.
Comment 2 iformanek 2005-11-24 15:29:47 UTC
Fixed in M11, the profiler module adding support for profiling nb modules did 
not work properly in Beta2/M10.

M11 containing this and other bugfixes will be released soon.
Comment 3 ehucka 2006-10-09 12:10:50 UTC
Verification of old issues.
Comment 4 Alexander Kouznetsov 2007-02-20 10:26:40 UTC
Closing old issues
Comment 5 Alexander Kouznetsov 2007-02-20 18:09:59 UTC
Reverting to original Target Milestone value changed by mistake. Sorry for
inconvenience.