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 77412 - CPU profilling does not produce correct result for complex applications
Summary: CPU profilling does not produce correct result for complex applications
Status: VERIFIED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-05 16:22 UTC by Tomas Hurka
Modified: 2007-04-03 10:14 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 Tomas Hurka 2006-06-05 16:22:05 UTC 
Lazy and Eager instrumentation scheme does not work for applications, which loads classes using more 
than one parent class loader. Example of such applications are NetBeans or Glassfish. Byte code analyzer 
in Lazy and Eager instrumentation uses classloader hierarchy to determine loaded classes. If this does not 
work correctly some classes are not instrumented by this schemes and the resulted profiling data is 
incorrect. The symptoms of this bug are excessive self time and calls to method which are not part of the 
source code.

Workaround: Use Total instrumentation scheme, which does not analyze bytecode.
Comment 1 Tomas Hurka 2006-06-05 16:24:11 UTC 
This is serious issue and should be fixed ASAP and the fix should be merged to release55 branch.
Comment 2 Tomas Hurka 2006-06-08 13:52:31 UTC 
Fixed in trunk. 
It will be merged to release55 early next week.
Comment 3 Tomas Hurka 2006-06-12 09:46:21 UTC 
Fix merged to release55 branch.
Comment 4 Tomas Hurka 2007-04-03 10:14:56 UTC 
Verified.