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.
This bug was originally marked as duplicate of bug 122043, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related. Build: NetBeans IDE 7.2 Beta (Build 201205031832) VM: Java HotSpot(TM) 64-Bit Server VM, 20.6-b01-415, Java(TM) SE Runtime Environment, 1.6.0_31-b04-415-11M3635 OS: Mac OS X User Comments: GUEST: Profiling memory GUEST: Called the memory profiler counting all allocations and saving the stack trace GUEST: Profiling a command line only Java app. Memory view. Application strains JVM heap with over 1GB data. Previous attempt to profile resulted in profiler hitting out of memory ex. erit01: Profiling a server running in eclipse GUEST: I tried to profile my application for memory usage, for a "project with existing ant script". The ant script has already been successfully modified to perform profiling (when I was using NB 5.5). The project has since been imported into NB 6.0 final, and on previous profiling invocations it worked successfully and did not encounter this problem. jamesvera: This error happend in 6.1 while browsing a heap dump GUEST: I'm runnin netbeans profiling. I also deleted some of the profile files inside the \dist directory as the size was huge. mrkam: Modified profiling mode from CPU to memory liveness while profiling Tomcat Web Application. mrkam: Was profiling AppletTest application in CPU mode, then switched to Memory Profiling and opened Live Results GUEST: profiling a very simple (sample) app, just playing with the IDE/profiler GUEST: starting application on jboss 4.X with garbage collection selected GUEST: Re-running the last profile session GUEST: Profiling an aplication using AspectJ plugin twolf2919: Tried to start memory profiling of main project and got this exception. jamesvera: I was browsing a heap dump GUEST: Profiling an application in JBoss GUEST: running the profiler on a memory-intensive app GUEST: It is a mystery, it was profiling an app, then i went to make a brew! GUEST: I was profiling a test program for java 3d. In this program, i created a huge amount of geometry data. GUEST: Taking a Snapshot in profiling mrkam: Modified profiling from CPU to Memory GUEST: viewing Live Profiling Results GUEST: Profiling. Stacktrace: java.lang.ArrayIndexOutOfBoundsException: 1199776 at org.netbeans.lib.profiler.results.memory.MemoryDataFrameProcessor.doProcessDataFrame(MemoryDataFrameProcessor.java:117) at org.netbeans.lib.profiler.results.AbstractDataFrameProcessor.processDataFrame(AbstractDataFrameProcessor.java:95) at org.netbeans.lib.profiler.results.ProfilingResultsDispatcher$2.run(ProfilingResultsDispatcher.java:164) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138)
Created attachment 120070 [details] stacktrace
Fixed in NetBeans 7.2.