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.
When performing CPU profiling on Windows, time values are limited to 2147483648 microseconds. To replicate this, create a simple app, like: public class Test { public static void main (String [] args) throws Exception { Thread.sleep (36000000); } } Start CPU profiling, then wait 40 minutes. Get the profiling results, the time column will show 2147483ms. I'm using NB profiler M5 on Windows XP SP2, Netbeans 4.0.
Ok, that's a correct observation, our user-level timing results are represented as in microseconds and as ints, so the timing for any individual method is limited to approximately 37 minutes. Interesting that this is the first report about this problem in more than 3 years this technology is publically available :-) We can address it as a part of issue 51274. Currently it would be too expensive to replace ints with longs in user-level data. But 51274 implementation will provide a better format for storing this data, and as a result we can use say 5 bytes instead of 4 bytes for method time. That should yield 37 min * 256 = 9472 min = 157 hours - probably enough for development-time profiling.
Fixed, updated code will become available in Milestone 7 release.
Verification of old issues.
Closing old issues.