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 60864 - CPU results are incorrect
Summary: CPU results are incorrect
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: iformanek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-12 10:33 UTC by iformanek
Modified: 2007-02-12 22:08 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 iformanek 2005-07-12 10:33:22 UTC 
As reported by Jess Hole:

Specifically, I get results and everything seems to work beautifully *except* 
my results don't make complete sense.  The results show methods directly under 
other methods which are not their direct parents.  I'm seeing enough of this 
that the results are all but useless in many cases.  I do have '-server' 
specified -- but I did with the instrumented 1.4.2_04 as well.
Comment 1 iformanek 2005-07-12 10:33:51 UTC 
Self assign for M8
Comment 2 iformanek 2005-08-18 15:22:41 UTC 
More details from Jess:

I am *guessing* that this should be easy to reproduce ala:

    "In 1.5.0_04 and milestone 7 I was trying to profile some JMX code I 
wrote.  The results shows javax.management.StandardMBean.setImplementation
(Object implementation,Class mbeanInterface) as a hotspot -- as I expected.  
Unfortunately, it shows many things directly under this method that are not 
directly called from this method.  This makes it impossible for me to tell 
what's really going on -- and to trust the results thus far..."

For a bit more specifics, basically what I did was subclassed StandardMBean and 
specified the constructor as a root method.  I then created an instance of this 
standard MBean per servlet request in Tomcat.  [Yes, I'm pushing for some fixes 
in StandardMBean based on this and subsequent nanoTime()-based metrics -- both 
to setImplementation and to getAttribute().]
Comment 3 iformanek 2005-08-30 16:56:59 UTC 
After more analysis, this seems to occur only under some special circumstances, 
lowering the priority to P2 to reflect this.
Comment 4 iformanek 2005-10-21 15:35:38 UTC 
This should no longer happen in M10
Comment 5 ehucka 2006-10-09 12:10:56 UTC 
Verification of old issues.
Comment 6 Alexander Kouznetsov 2007-02-12 22:08:43 UTC 
Closing old issues.