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.
Sometimes (unfortunately I cannot reliably reproduce this) the profiler shows ridiculous high execution times, e.g. 510185365 ms which makes the timings not really usable. Switching between JDK 1.5 and JDK 1.6 does not change this. Once the Profiler "goes" into this mode, it cannot get it to work properly again unless I start with a fresh userdir. This has happened with 6.0 also sometimes.
Created attachment 60913 [details] Sample snapshot with invalid timings
Do you have dynamic CPU frequency switching (PowerNow!/SpeedStep) enabled on your system? The problem typically occurs when the calibration data are incorrect. You should try to re-calibrate the profiler (Profile | Advanced Commands | Run Profiler Calibration) and definitely disable dynamic CPU freq. sw. during profiling if enabled. If the re-calibration doesn't help, could you please provide a sample code which reproduces the problem? Also please attach the IDE logfile, it contains important data about your system (OS/JDK version etc.).
Yes I do have a CPU with dynamic freq. but for the tests I have disabled the switching and the CPUs were running at full speed. After disabling the dynamic frequency I re-run the calibration. But I still get these strange figures. The next time it occurs I will attach the IDE log file.
Can you also attach code for that long method? Is it always the same one?
Would it be possible to get the code for reproducible test case? Without that it's rather impossible to find the root cause. Thanks.
no response for more than a year - closing invalid. If encountered again, please reopen.