Thanks Mikhail. And that's exactly how I intended to using it when I found out the problem :-)
Now, if you don't mind sharing: how do you go about logging gc (which is done already using the param --log_gc) and most importantly analyzing the log dumps? Thanks again for your help. On Feb 1, 2:29 am, Mikhail Naganov <mnaga...@chromium.org> wrote: > Hi LDS, > > 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. > > > > > > > > On Tue, Jan 31, 2012 at 18:57, LDS <ldese...@gmail.com> wrote: > > To the best of my knowledge, this line in process-heap-prof: > > > if row[0] == 'heap-sample-begin' and row[1] == 'Heap': > > > won't parse correctly the v8.log output generated with --log_all > > option as it seems that v8 won't output Heap (when did that happen?) > > > Was "Heap" replaced with "NewSpace"? Please advise. > > > Thanks, > > > LdS > > > -- > > v8-users mailing list > > v8-users@googlegroups.com > >http://groups.google.com/group/v8-users -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users
