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 248816 - [HeapWalker] ArrayIndexOutOfBoundsException: -71
Summary: [HeapWalker] ArrayIndexOutOfBoundsException: -71
Status: REOPENED
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-11-21 18:49 UTC by Jesse Glick
Modified: 2017-03-22 09:25 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 213172


Attachments
stacktrace (1.02 KB, text/plain)
2014-11-21 18:49 UTC, Jesse Glick
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2014-11-21 18:49:16 UTC
Build: NetBeans IDE Dev (Build 20141110-6ca365d62b59)
VM: Java HotSpot(TM) 64-Bit Server VM, 24.65-b04, Java(TM) SE Runtime Environment, 1.7.0_67-b01
OS: Linux

User Comments:
sebglon: Load hprof file Java7

jglick: Right-clicked Open on an hprof file. Did not open.




Stacktrace: 
java.lang.ArrayIndexOutOfBoundsException: -71
   at org.netbeans.lib.profiler.heap.HprofHeap.fillTagBounds(HprofHeap.java:1051)
   at org.netbeans.lib.profiler.heap.HprofHeap.<init>(HprofHeap.java:133)
   at org.netbeans.lib.profiler.heap.HeapFactory.createHeap(HeapFactory.java:87)
   at org.netbeans.lib.profiler.heap.HeapFactory.createHeap(HeapFactory.java:69)
   at org.netbeans.modules.profiler.heapwalk.HeapWalker.createHeap(HeapWalker.java:193)
   at org.netbeans.modules.profiler.heapwalk.HeapWalker.<init>(HeapWalker.java:92)
Comment 1 Jesse Glick 2014-11-21 18:49:18 UTC
Created attachment 150616 [details]
stacktrace
Comment 2 Tomas Hurka 2014-11-24 08:15:45 UTC
It looks like it is caused by broken heap dump. If not, can you provide steps how to
reproduce it? Can you attach the heap dump, which fails with reported AIOOBE?
Thanks.
Comment 3 Jesse Glick 2014-11-25 18:28:37 UTC
Indeed it only happens with this one heap dump. The contents are confidential so I cannot attach it. Regardless of what the contents are, the code should be written defensively against malformed input and provide some kind of human-facing error message, if only “something about this heap dump seems to be corrupt”.
Comment 4 Exceptions Reporter 2017-03-22 09:25:07 UTC
This bug already has 5 duplicates 
see http://statistics.netbeans.org/exceptions/detail.do?id=213172