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 224079, 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.4 (Build 201310111528) VM: Java HotSpot(TM) 64-Bit Server VM, 24.45-b08, Java(TM) SE Runtime Environment, 1.7.0_45-b18 OS: Windows 7 User Comments: aquaglia: Trying to stop profiling https://netbeans.org/bugzilla/show_bug.cgi?id=236118 Stacktrace: java.lang.ArrayIndexOutOfBoundsException: 5524 at org.netbeans.lib.profiler.ui.memory.MemoryResultsPanel.sortResultsByClassName(MemoryResultsPanel.java:553) at org.netbeans.lib.profiler.ui.memory.LivenessResultsPanel.getResultsSortedByClassName(LivenessResultsPanel.java:218) at org.netbeans.lib.profiler.ui.memory.LivenessResultsPanel.getResultsSortedByLiveObjSize(LivenessResultsPanel.java:260) at org.netbeans.lib.profiler.ui.memory.LivenessResultsPanel.sortResults(LivenessResultsPanel.java:696) at org.netbeans.lib.profiler.ui.memory.LivenessResultsPanel.getResultsTable(LivenessResultsPanel.java:349) at org.netbeans.lib.profiler.ui.memory.MemoryResultsPanel.prepareResults(MemoryResultsPanel.java:184)
Created attachment 143028 [details] stacktrace
*** Bug 239420 has been marked as a duplicate of this bug. ***
Please provide steps how to reproduce it. Without this steps we are not able to investigate it. Thanks.
Start profiling a java project, with allocation stack trace. Click on live results. After a few seconds right click on the first line of the Live Allocated Objects (it is a char[] in my case) Nothing happens. After a one or two minutes of waiting time right click on the same row and choose "Stop tracing this class". An exception is reported.
What does it mean 'Nothing happens.'? Does it mean that there is popup?
Start profiling a java project, with allocation stack trace. Click on live results. After a few seconds right click on the first line of the Live Allocated Objects (it is a char[] in my case) and click on "Take Snapshots and Show Allocation Stack Traces". Nothing happens, in the sense that the allocations tab is not shown. If you right click again on the same class, the spinning wheel is shown. After one or two minutes of waiting time right click on the same row and choose "Stop tracing this class". An exception is reported in the status bar, on the right. I click on the "1" inside the small balloon and the Notifications tab is comes into focus showing and unexpected exception. After that Netbeans becomes unstable. If I try to stop the profiling NB becomes extremely sluggish and needs to be restarted.
I see. You did not mentioned "Take Snapshots and Show Allocation Stack Traces" before. I was trying to reproduce it using your steps, but I was not successful. Can you please attach test project, where this can be reproduced. Thanks.
I guess that you need to be profiling a memory intensive project that performs many xslt transformations and uses JABX bindings. I cannot really attach my project since it has not been published, yet, and it uses commercial libraries that require a license. If you really need my project to proceed, then it will have to wait until publication. I am a bit surprised though that that is the only way you can follow, considering the amount of diagnostic information I have uploaded. This relates to https://netbeans.org/bugzilla/show_bug.cgi?id=236118
I am sorry, but from the gathered information, it is not clear what caused this ArrayIndexOutOfBoundsException. We need reproducible test case, this is the only way how to find out what is going on and fix it. It will be also beneficial for you, since we will be able to verify the fix. Closing as incomplete until we have the reproducible test case.
Fine for me, thanks.
Actually, the status RESOLVED/INCOMPLETE is inappropriate. The bug is it is logged by the exceptions reporter of NetBeans. I detailed the steps and I can reproduce it at any time. So, I think this bug should remain open until solved.
It does not help us that you are able to reproduce it. Incomplete means that the bug cannot be fixed until more information is available. This is exactly this case - we are waiting for test project or more detailed steps, which will allow us to reproduce this issue. Until we are able to reproduce it, this issue should remain in incomplete state.
But don't you find it disturbing that it shows as resolved, while the problem is there?
No, this is how resolved/incomplete is defined.
(In reply to aquaglia from comment #9) [..] > If you really need my project to proceed, then it will have to wait until > publication. Is there anything new? Is your project available somewhere, so we can try your test case?