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.
Profiler 1.2 070710 Product Version: NetBeans IDE Dev (Build 200707110000) Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b05 System: SunOS version 5.10 running on x86; ISO646-US; en (nb) Unfortunately, I was not able to reproduce this issue after I restarted IDE, but I run into the situation when each time after I performed Memory Liveness Profiling for AnagramGame Test I got the following exception and snapshot was not opened. The same time profiling and test states were shown as Running. The exception was thrown right after I confirmed "Profiled Application finished. Would you like to obtain snapshot" dialog. Exception in thread "Thread-52" java.lang.ArrayIndexOutOfBoundsException: 1431 at com.sun.tools.profiler.results.memory.MemoryCCTProvider$ObjectNumbersContainer.<init>(MemoryCCTProvider.java:87) at com.sun.tools.profiler.results.memory.MemoryCallGraphBuilder.getLivenessObjectNumbers(MemoryCallGraphBuilder.java:203) ...
Created attachment 44979 [details] Exception
P4 until it is reproduced again.
Reproduced with the following steps: - Started Analyze Memory Liveness: track each 1 object, record allocation stack traces for Web Application - Opened Live Results as soon as button got enabled - RESULT: Exception is thrown: java.lang.ArrayIndexOutOfBoundsException: 1288 at com.sun.tools.profiler.results.memory.MemoryCCTProvider$ObjectNumbersContainer.<init>(MemoryCCTProvider.java:87) ...
Created attachment 45013 [details] Exception
Reproduced again on Solaris SPARC, Live Results were opened when I started new profiling session and got this AIOOBE.
Live Results window is empty once this exception was thrown. User needs to restart or modify profiling session to obtain Live Results.
This issue is highly reproducible with Product Version: NetBeans IDE Dev (Build 200708150158) Java: 1.6.0_01; Java HotSpot(TM) Client VM 1.6.0_01-b06 System: SunOS version 5.10 running on sparc; ISO8859-1; en_US (nb)
It seems that the most reproducible scenario is on the second run of Liveness Memory Profiling when Live results window is already opened.
this had the same root cause as the issue #114751 it is fixed in trunk now