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 155129 - NullPointerException at org.netbeans.lib.profiler.heap.ThreadObjectHprofGCRoot.getStackTrace
Summary: NullPointerException at org.netbeans.lib.profiler.heap.ThreadObjectHprofGCRoo...
Status: RESOLVED WORKSFORME
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Petr Cyhelsky
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-10 13:02 UTC by Petr Cyhelsky
Modified: 2009-04-16 09:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 144189

Attachments
stacktrace (531 bytes, text/plain)
2008-12-10 13:02 UTC, Petr Cyhelsky 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Cyhelsky 2008-12-10 13:02:03 UTC 
Build: NetBeans IDE Dev (Build 081209)
VM: Java HotSpot(TM) Client VM, 1.5.0_17-b02, Java(TM) 2 Runtime Environment, Standard Edition, 1.5.0_17-b02
OS: Windows Vista, 6.0, x86

User Comments:
cyhelsky: loading heapdump taken via VisualVM



Stacktrace: 
java.lang.NullPointerException
        at org.netbeans.lib.profiler.heap.ThreadObjectHprofGCRoot.getStackTrace(ThreadObjectHprofGCRoot.java:64)
        at org.netbeans.modules.profiler.heapwalk.ThreadsController.getStackTrace(ThreadsController.java:111)
        at org.netbeans.modules.profiler.heapwalk.ui.ThreadsControllerUI$1.run(ThreadsControllerUI.java:127)
        at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:573)
        at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1005)
Comment 1 Petr Cyhelsky 2008-12-10 13:02:13 UTC 
Created attachment 74800 [details]
stacktrace
Comment 2 Petr Cyhelsky 2009-04-16 09:40:04 UTC 
No longer reproducible with any heap dump, seems that the original heap dump was somehow corrupted.