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.

Bug 232890 - ArrayIndexOutOfBoundsException: -1
Summary: ArrayIndexOutOfBoundsException: -1
Status: NEW
Alias: None
Product: profiler
Classification: Unclassified
Component: Engine (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-17 09:06 UTC by Jiri Skrivanek
Modified: 2015-04-24 09:43 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 202221

Attachments
stacktrace (1.84 KB, text/plain)
2013-07-17 09:06 UTC, Jiri Skrivanek 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Skrivanek 2013-07-17 09:06:52 UTC 
Build: NetBeans IDE Dev (Build 201307162300)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.25-b01, Java(TM) SE Runtime Environment, 1.7.0_25-b15
OS: Windows 7

User Comments:
jskrivanek: I tried to modify attached profiling session from CPU to Memory with opened empty live results.




Stacktrace: 
java.lang.ArrayIndexOutOfBoundsException: -1
   at org.netbeans.lib.profiler.classfile.ClassLoaderTable.getParentLoader(ClassLoaderTable.java:81)
   at org.netbeans.lib.profiler.classfile.SameNameClassGroup.isParentLoaderTo(SameNameClassGroup.java:145)
   at org.netbeans.lib.profiler.classfile.SameNameClassGroup.checkForCompatibility(SameNameClassGroup.java:87)
   at org.netbeans.lib.profiler.classfile.ClassRepository.lookupClassOrCreatePlaceholder(ClassRepository.java:468)
   at org.netbeans.lib.profiler.instrumentation.ClassManager.javaClassOrPlaceholderForName(ClassManager.java:223)
   at org.netbeans.lib.profiler.instrumentation.MemoryProfMethodInstrumentor$MethodScanerForNewOpcodes.hasNewArrayOpcodes(MemoryProfMethodInstrumentor.java:87)
Comment 1 Jiri Skrivanek 2013-07-17 09:06:53 UTC 
Created attachment 137306 [details]
stacktrace
Comment 2 Jiri Kovalsky 2015-04-24 09:43:37 UTC 
I have encountered this same exception too. Here are my steps to reproduce the exception:

1. Launch NetBeans IDE and launch VisualVM 1.3.8 too.
2. In VisualVM's "Applications" view right click "NetBeans IDE" node and invoke "Sample" from its popup menu.
3. Switch to "Profiler" view and click "CPU" button.
4. After say 5 seconds, click "Stop" button and wait while status is saying "refreshing" until "CPU" button is enabled again.
5. Then push the "CPU" button quickly again. After a while you will notice "Profiler Busy" in the status bar at 50% accompanied with the IOOBE -1.

As a consequence the NetBeans IDE will become unresponsive and you will have to kill it.