Closed Bug 562983 Opened 14 years ago Closed 6 years ago

Profiler should expose which references are weak references

Categories

(Tamarin Graveyard :: Profiler, defect, P3)

Product:
Tamarin Graveyard
Component:
Profiler
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX
Milestone:
Q2 12 - Cyril

People

(Reporter: mike, Assigned: jbahuley)

References

Details

See http://bugs.adobe.com/jira/browse/FB-26778 -- the profiler API currently does not expose a way for a client profiler to tell the difference between weak references and regular (non-weak) ones.  This can be very important, because when tracing the path of an object to the GC root, what you usually want to know is which paths are forcing the object to be held in memory; and weak references do not force the object to be held.
Blocks: Profiler_bugs
Flags: flashplayer-qrb+
Priority: -- → P3
Target Milestone: --- → flash10.2
Assignee: nobody → mmoreart
Status: NEW → ASSIGNED
Assignee: mmoreart → nobody
Component: Virtual Machine → Profiler
QA Contact: vm → profiler
Flags: flashplayer-bug-
Target Milestone: Q3 11 - Serrano → Q1 12 - Brannan
Assignee: nobody → jbahuley
Target Milestone: Q1 12 - Brannan → Q2 12 - Cyril
(given the changes in the sampler infrastructure, several of these bugs might be able to be closed as wontfix.)
Status: ASSIGNED → NEW
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.