<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: Heap Snapshot should be able to tell me if an object was collected"
href="https://bugs.webkit.org/show_bug.cgi?id=163151#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: Heap Snapshot should be able to tell me if an object was collected"
href="https://bugs.webkit.org/show_bug.cgi?id=163151">bug 163151</a>
from <span class="vcard"><a class="email" href="mailto:ggaren@apple.com" title="Geoffrey Garen <ggaren@apple.com>"> <span class="fn">Geoffrey Garen</span></a>
</span></b>
<pre><span class="quote">> Showing the dead objects in the tree was very distracting though, since we
> couldn't preview what they were. On even a small page, there could be
> hundreds of objects cluttering the object graphs.</span >
Perhaps we could fix this by making live vs dead an option. I can imagine situations where I would want to focus on one or the other.
Another option would be to snapshot object previews at snapshot time. So, if an object had properties { A, B } at snapshot time, and then acquired a property C => { A, B, C }, the snapshot would still show { A, B }.
Some of this goes to the question of what "snapshot" means. Something that updates over time is not a snapshot -- so it may be a misleading word for our current feature. Our current feature is a bag of objects that grows or shrinks as those objects acquire properties or die.
<span class="quote">> Would it help to have a live and dead memory total, but only have the tree
> show the live objects?</span >
Yeah, that might help. It might also help to groups dead objects into some more compact form that doesn't clutter the UI, but still indicates that a bunch of your snapped objects die.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>