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.
If I choose Profile > Load Heap Dump and then choose a file that is *not* a valid JVM heap dump file, the Profiler does not fail gracefully. Either I get: 1. Nothing - no feedback at all or 2. An exception. One example is below: java.nio.BufferUnderflowException at java.nio.Buffer.nextGetIndex(Buffer.java:474) at java.nio.DirectByteBuffer.get(DirectByteBuffer.java:205) at com.sun.tools.profiler.heap.HprofMappedByteBuffer.readStringNull(HprofMappedByteBuffer.java:65) at com.sun.tools.profiler.heap.HprofMappedByteBuffer.readHeader(HprofMappedByteBuffer.java:45) at com.sun.tools.profiler.heap.HprofMappedByteBuffer.<init>(HprofMappedByteBuffer.java:40) at com.sun.tools.profiler.heap.HprofHeap.<init>(HprofHeap.java:85) at com.sun.tools.profiler.heap.HeapFactory.createHeap(HeapFactory.java:48) at com.sun.tools.profiler.heap.HeapFactory.createHeap(HeapFactory.java:31) at org.netbeans.modules.profiler.heapwalk.HeapWalker.createHeap(HeapWalker.java:158) at org.netbeans.modules.profiler.heapwalk.HeapWalker.<init>(HeapWalker.java:50) at org.netbeans.modules.profiler.heapwalk.ui.OpenHeapWa Seems like if the file is not a binary heap dump file then the Profiler should display an appropriate error message.
Yes, some kind of warning is needed.
*** This issue has been marked as a duplicate of 92576 ***