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 60265 - Allocation stack traces can be empty if the memory snapshot is taken early
Summary: Allocation stack traces can be empty if the memory snapshot is taken early
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: All All
: P2 blocker (vote)
Assignee: iformanek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-20 12:01 UTC by iformanek
Modified: 2007-02-12 22:02 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 iformanek 2005-06-20 12:01:15 UTC 
Allocation stack traces are always empty even if they are turned on, both for 
liveness and allocation memory profiling.
Comment 1 iformanek 2005-06-20 12:01:56 UTC 
Needs to be fixed for M7
Comment 2 iformanek 2005-06-22 15:59:26 UTC 
Changed the summary to better reflact the symptom.

If the memory snapshot is taken soon after the app starts, there are memory 
results, but the stack traces do not show any allocation call path below the 
root node (object).
Comment 3 iformanek 2005-06-22 17:31:16 UTC 
Still happens
Comment 4 iformanek 2005-06-23 11:51:39 UTC 
Postponing to M8
Comment 5 iformanek 2005-09-16 16:13:21 UTC 
This does not happen anymore, it was probably fixed as a sideffect of other fix.
Comment 6 ehucka 2006-10-09 12:09:04 UTC 
Verification of old issues.
Comment 7 Alexander Kouznetsov 2007-02-12 22:02:47 UTC 
Closing old issues.