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 246746 - ArrayIndexOutOfBoundsException: 15
Summary: ArrayIndexOutOfBoundsException: 15
Status: VERIFIED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Engine (show other bugs)
Version: 8.1
Hardware: All All
: P3 normal (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-28 09:02 UTC by Jiri Skrivanek
Modified: 2014-09-15 10:26 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 211483


Attachments
stacktrace (1.33 KB, text/plain)
2014-08-28 09:02 UTC, Jiri Skrivanek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Skrivanek 2014-08-28 09:02:13 UTC
This bug was originally marked as duplicate of bug 229910, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE Dev (Build web-main-1212-on-20140828)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.20-b23, Java(TM) SE Runtime Environment, 1.8.0_20-b26
OS: Windows 7

User Comments:
jskrivanek: jskrivanek: My Steps:
- create Paint Application sample project
- right-click project node and choose Profile
- activate Multiple features and  select Threads and Locks
- click Profile to start profiling
- switch several times Threads and Locks view
- add Telemetry view
- add Methods view and exception is thrown




Stacktrace: 
java.lang.ArrayIndexOutOfBoundsException: 15
   at org.netbeans.lib.profiler.results.cpu.CPUCallGraphBuilder.waitEntry(CPUCallGraphBuilder.java:621)
   at org.netbeans.lib.profiler.results.cpu.CPUCallGraphBuilder.monitorEntry(CPUCallGraphBuilder.java:362)
   at org.netbeans.lib.profiler.results.locks.AbstractLockDataFrameProcessor$1.execute(AbstractLockDataFrameProcessor.java:58)
   at org.netbeans.lib.profiler.results.AbstractDataFrameProcessor.foreachListener(AbstractDataFrameProcessor.java:177)
   at org.netbeans.lib.profiler.results.locks.AbstractLockDataFrameProcessor.fireMonitorEntry(AbstractLockDataFrameProcessor.java:56)
   at org.netbeans.lib.profiler.results.cpu.CPUSamplingDataFrameProcessor.doProcessDataFrame(CPUSamplingDataFrameProcessor.java:194)
Comment 1 Jiri Skrivanek 2014-08-28 09:02:15 UTC
Created attachment 148933 [details]
stacktrace
Comment 2 Tomas Hurka 2014-09-05 13:29:04 UTC
Fixed in profiler-main:

changeset:   277517:cf1203eb1d1d
user:        Tomas Hurka <thurka@netbeans.org>
date:        Fri Sep 05 15:19:41 2014 +0200
summary:     bugfix #246746, locks monitoring and cpu sampling must use same thread ids
Comment 3 Quality Engineering 2014-09-06 04:54:23 UTC
Integrated into 'main-silver', will be available in build *201409060001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/cf1203eb1d1d
User: Tomas Hurka <thurka@netbeans.org>
Log: bugfix #246746, locks monitoring and cpu sampling must use same thread ids