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 235167 - ArrayIndexOutOfBoundsException: 560
Summary: ArrayIndexOutOfBoundsException: 560
Status: RESOLVED FIXED
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-08-28 12:19 UTC by Petr Cyhelsky
Modified: 2014-02-12 09:39 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 203398


Attachments
stacktrace (1.38 KB, text/plain)
2013-08-28 12:19 UTC, Petr Cyhelsky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Cyhelsky 2013-08-28 12:19:41 UTC
Build: NetBeans IDE Dev (Build 201308260001)
VM: OpenJDK 64-Bit Server VM, 23.7-b01, OpenJDK Runtime Environment, 1.7.0_25-b30
OS: Linux

User Comments:
cyhelsky: reproducing bug #234784 (steps are there) under monitored IDE (with lock contention monitoring on) -> clicking on monitor *unknown* in Lock Contention view




Stacktrace: 
java.lang.ArrayIndexOutOfBoundsException: 560
   at org.netbeans.lib.profiler.results.locks.LockGraphBuilder.getThreadInfo(LockGraphBuilder.java:269)
   at org.netbeans.lib.profiler.results.locks.LockGraphBuilder.monitorEntry(LockGraphBuilder.java:120)
   at org.netbeans.lib.profiler.results.locks.AbstractLockDataFrameProcessor$1.execute(AbstractLockDataFrameProcessor.java:58)
   at org.netbeans.lib.profiler.results.AbstractDataFrameProcessor.foreachListener(AbstractDataFrameProcessor.java:175)
   at org.netbeans.lib.profiler.results.locks.AbstractLockDataFrameProcessor.fireMonitorEntry(AbstractLockDataFrameProcessor.java:56)
   at org.netbeans.lib.profiler.results.locks.LockDataFrameProcessor.doProcessDataFrame(LockDataFrameProcessor.java:126)
Comment 1 Petr Cyhelsky 2013-08-28 12:19:42 UTC
Created attachment 139369 [details]
stacktrace
Comment 2 Tomas Hurka 2014-02-12 09:39:26 UTC
It looks like this is fixed in 8.0. Please reopen if you are able to reproduce it with latest dev. build. Thanks.