Jens,
another thing you should be aware of is that DOM nodes are only
collected on full garbage collections. In order to see what is
actually live at the end of a test, you have to force a number of GCs.
If you run in the test shell with the --js-flags=--expose-gc flag,
you can force gc's by
Sending from proper account, sorry.
On Wed, Sep 23, 2009 at 1:05 PM, Anton Muhin ant...@google.com wrote:
In your case there should be not that many DOM windows objects and
they all should survive in batches, so if I'd face such a problem, I'd
just put a break point to see why this object got
On Sep 23, 2009, at 12:32 AM, Mads Sig Ager wrote:
another thing you should be aware of is that DOM nodes are only
collected on full garbage collections. In order to see what is
actually live at the end of a test, you have to force a number of GCs.
But the GC should happen automatically
On Wed, Sep 23, 2009 at 7:02 PM, Jens Alfke s...@google.com wrote:
On Sep 23, 2009, at 12:32 AM, Mads Sig Ager wrote:
another thing you should be aware of is that DOM nodes are only
collected on full garbage collections. In order to see what is
actually live at the end of a test, you have
On Wed, Sep 23, 2009 at 2:21 AM, Jens Alfke s...@google.com wrote:
On Sep 22, 2009, at 2:54 PM, Mikhail Naganov wrote:
I'm working on showing JS objects retainers. But this only works for
objects that live inside V8's heap.
That would still be useful — I'd love to be able to look at all
I'm working on showing JS objects retainers. But this only works for
objects that live inside V8's heap. I'm not considering links between
JS wrappers and C++ objects. I know Vitaly (cc'ed) wanted to do
something about such cycles.
On Wed, Sep 23, 2009 at 01:47, Jens Alfke s...@google.com wrote:
On Sep 22, 2009, at 2:54 PM, Mikhail Naganov wrote:
I'm working on showing JS objects retainers. But this only works for
objects that live inside V8's heap.
That would still be useful — I'd love to be able to look at all the
'Window' objects in the heap and what ref chain is keeping them
Because we have C++ and JS wrappers, and there may be references known to
the C++ side not known to the JS side, we have to do an object grouping
before we can call GC. This grouping takes all wrappers and groups them by
their root; and then they are collected together. This happens in
