You are absolutely correct. The change happened around the Isolates
branch merge. Actually, this script isn't actively used. Previously,
it was intended to be used with "--log_gc" flag.
> --
> v8-users mailing list
> v8-u...@googlegroups.com
> http://groups.google.com/group/v8-users
If you want to investigate what comprises your heap in details, I
would advice you either to use heap profiler from Chrome Developer
Tools (tip: run canary or dev channel version of Chrome -- DevTools
evolve pretty fast), or Node inspector for node.js.
The reason why you can no more use log_gc out of the box is that after
the new GC algorithm was introduced in V8, heap is no more iterable at
arbitrary moments -- you need to perform a special round of GC for
that, so logging heap statistics continuously will require some
tweaking. I'm not saying it's impossible, but perhaps you can achieve
your goals without messing with this outdated logging feature.