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 203068 - ArrayIndexOutOfBoundsException: 8
Summary: ArrayIndexOutOfBoundsException: 8
Status: RESOLVED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 7.0
Hardware: All All
: P3 normal (vote)
Assignee: issues@profiler
URL:
Keywords: RANDOM
: 249753 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-10-04 15:24 UTC by Petr Cyhelsky
Modified: 2015-04-21 13:24 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 181605


Attachments
stacktrace (1.24 KB, text/plain)
2011-10-04 15:24 UTC, Petr Cyhelsky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Cyhelsky 2011-10-04 15:24:21 UTC
Build: NetBeans IDE Dev (Build 201110020601)
VM: Java HotSpot(TM) 64-Bit Server VM, 21.0-b18, Java(TM) SE Runtime Environment, 1.7.0-b148
OS: Linux

Stacktrace: 
java.lang.ArrayIndexOutOfBoundsException: 8
   at org.netbeans.lib.profiler.results.cpu.CPUCallGraphBuilder.methodEntry(CPUCallGraphBuilder.java:204)
   at org.netbeans.lib.profiler.results.cpu.CPUDataFrameProcessor$2.execute(CPUDataFrameProcessor.java:398)
   at org.netbeans.lib.profiler.results.AbstractDataFrameProcessor.foreachListener(AbstractDataFrameProcessor.java:164)
   at org.netbeans.lib.profiler.results.cpu.CPUDataFrameProcessor.fireMethodEntry(CPUDataFrameProcessor.java:396)
   at org.netbeans.lib.profiler.results.cpu.CPUDataFrameProcessor.doProcessDataFrame(CPUDataFrameProcessor.java:165)
   at org.netbeans.lib.profiler.results.AbstractDataFrameProcessor.processDataFrame(AbstractDataFrameProcessor.java:93)
Comment 1 Petr Cyhelsky 2011-10-04 15:24:26 UTC
Created attachment 111468 [details]
stacktrace
Comment 2 Tomas Hurka 2015-04-21 12:57:18 UTC
*** Bug 249753 has been marked as a duplicate of this bug. ***
Comment 3 Tomas Hurka 2015-04-21 13:14:45 UTC
This issue should be fixed in dev. build.
Comment 4 Tomas Hurka 2015-04-21 13:24:59 UTC
*** Bug 249753 has been marked as a duplicate of this bug. ***