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 60025 - Take Snapshot throws NPE
Summary: Take Snapshot throws NPE
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-15 12:27 UTC by ehucka
Modified: 2006-03-24 12:51 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
ide log fragment (2.62 KB, text/plain)
2005-06-15 12:28 UTC, ehucka 		Details
another npe's stacktrace (2.68 KB, text/plain)
2005-06-15 12:33 UTC, ehucka 		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 ehucka 2005-06-15 12:27:15 UTC 
NB 4.1, Profiler dev 050615, JDK 1.5.0_04, Linux FC3

After I started Memory Profiling of main project (Record GC and object creation)
and I opened Live Results window the NPE began periodicaly throwing and no
results wwere displayed in results window.
Comment 1 ehucka 2005-06-15 12:28:19 UTC 
Created attachment 22698 [details]
ide log fragment
Comment 2 ehucka 2005-06-15 12:32:10 UTC 
When I invoke Take Snapshot there was thrown another NPE. Maybe it is related to
this issue.
Comment 3 ehucka 2005-06-15 12:33:08 UTC 
Created attachment 22699 [details]
another npe's stacktrace
Comment 4 iformanek 2005-06-16 09:22:26 UTC 
The first part of this issue is fixed, the second part (unrelated) I cannot 
reproduce, it may have gone away - if you get a reproducible case, please 
reopen this issue and change its summary.
Comment 5 ehucka 2005-06-16 13:06:19 UTC 
I found if I invoke Take snapshot button immediately after it is enabled in
profiler start sometimes there is thrown the second NPE:

java.lang.NullPointerException
java.lang.System.arraycopy(Native Method)
com.sun.tools.profiler.results.memory.ObjLivenessCallGraphBuilder$ObjectNumbersContainer.<init>(ObjLivenessCallGraphBuilder.java:259)
...

It seems that it is enabled too early because the Basic Telemetry usualy shows O
Classes instrumented or some its values are just changing.
Comment 6 iformanek 2005-06-20 12:11:46 UTC 
Still cannot reproduce this even if I try to do this programmatically at the 
earliest possible time. Changing back to fixed until (if) it occurs again.
Comment 7 ehucka 2005-06-20 13:12:16 UTC 
i cannot reproduce both scenarios in 050620