Issue 2738 in v8: Cyclic reference that the GC does not detect properly

[codesite...@google.com]

Status: New
Owner: ----

New issue 2738 by alberto....@gmail.com: Cyclic reference that the GC does
not detect properly
http://code.google.com/p/v8/issues/detail?id=2738

When I execute

node --trace_gc --trace_gc_verbose leak.js

the following code inside leak.js causes the memory grows up to the limit
and 40 second later finish:

var a = new Object();
for (var i = 0; i < 16227663; i++)
{
a[i] = new Array();
}

The GC is releasing memory properly?

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[codesite...@google.com]

Updates:
Status: WorkingAsIntended

Comment #1 on issue 2738 by yan...@chromium.org: Cyclic reference that the

GC does not detect properly
http://code.google.com/p/v8/issues/detail?id=2738

all created arrays stay reachable though the object a which hangs off the
global object, so nothing can be thrown away. V8's GC is close to wizardry,
but not *that* magical just yet. There is no cyclic reference I can see.