Updates:
Cc: [email protected]
Comment #1 on issue 2077 by [email protected]: The scavenger GC does not
collect independent DOM objects
http://code.google.com/p/v8/issues/detail?id=2077
Due to API semantics we can't reclaim weakly reachable object immediately.
One GC is required to discover them and if weak callbacks will not
resurrect them they will be reclaimed by the next GC. This is why weakly
reachable objects are copied around (and promoted) during scavenge. Also
once weakly reachable object was promoted next scavenge will not be able to
reclaim it and full collection will be required.
To work around that the whole semantics of weak-callback API has to be
changed, but I am not sure that this is possible.
Looping in Anton, who has an excessive knowledge of bindings layer. Anton,
does binding layer really need an ability to ressurect weakly reachable
objects and execute arbitrary JavaScript in weak callbacks?
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
