I was planning on using it through d8, connected to a running node instance. I couldn't find much information on liveobjectlist but based on the name and looking at the code I figured it could be a good tool for tracking down memory issues. Mikhail pointed me to node-inspector, though, which turned me on to the v8-profiler module which is the tool I was looking for. I was just surprised this wasn't built-in to d8!
Thanks! On Sat, May 14, 2011 at 7:52 AM, Mark Lam (Palm GBU) <[email protected]>wrote: > Hi Marcel, > I contributed the liveobjectlist code. I’ll try to spend some time on it > this weekend and see if I can get it up to date. While I’m looking into it, > was there some aspect of it that you were particularly interested and how > you were planning to use it (via d8? Remotely?) that I should pay attention > to? > > Thanks. > > Mark > > > > On 5/13/11 12:51 PM, "Marcel Laverdet" <[email protected]> wrote: > > Does anyone have any tips for debugging applications whose memory usage > just grows and grows? I don't really have a good lead on the issue, so I > don't know where to start. Perhaps a way to find large collections of > festering objects, old generational objects, or other tools? > > Peaking at the v8 debug options I found "liveobjectlist" which sounds > promising, but seems that hasn't compiled cleanly in some time (or maybe I'm > just missing something). > > Any advice appreciated :) > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
