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.
Live results of cpu profiling (mostly of code with wait/sleep) are nonlogicaly changing. I assume that self time of a method always increasing but there are sometimes values less than a step before or sometimes it jump to zero. After the application finished it shows the right value. example: jfluid/test/functional/data/projects/j2se-simple, class: WaitingTest, method: method1000()
This has been fixed by bugfix for issue 67197
I can reproduce it with code using wait/sleep manualy and by automated tests in dev build 051101.
Fixed in M10. This was a sideeffect of removing cleansing of time at the get results moment.
Some automated tests are still failing but the 'fluctuations' are only in nano seconds. So I can rewrite automated tests to ignore nano seconds but it is strange that there can occure such case.
is this issue still valid for profiler trunk?
Automated tests on solaris sparc last week failed by this issue. It measured: method invocations time(us) 1. step simple.CPU.test500() 3 1525180 2. step simple.CPU.test500() 4 1525179 where 'step' is update of live results.
Ok, I will investgate.
Changing target milestone to dev, since NetBeans 6.0 is in high resistance mode.