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 79210 - [ProfilingPoints] start/stop timing clobbered by CPU instrumentation
Summary: [ProfilingPoints] start/stop timing clobbered by CPU instrumentation
Status: NEW
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks: 79229
  Show dependency tree
 
Reported: 2006-06-27 13:54 UTC by Tomas Hurka
Modified: 2011-11-02 20:22 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-27 13:54:30 UTC 
Start/stop profiling points results are clobbered by underlying CPU instrumentation. Time measured by 
start/stop profining points contains time spent in profiler runtime classes and in TCP/IP communication 
with NetBeans.
Comment 1 Tomas Hurka 2007-09-27 17:43:14 UTC 
The worst case (when TA communicate with profiler client) is now fixed. There is still some small discrepancy between time measured between two 
stopwatches and time reported by CPU profiling. Lowering priority to P3.