There is a Node Inspector project (https://github.com/dannycoates/node-inspector) based on Inspector / DevTools. I'm not aware of its current capabilities.
On Fri, May 13, 2011 at 13:06, Marcel Laverdet <[email protected]> wrote: > This is actually a Node application.. is it possible to wire Chromium up to > browse the heap of an outside v8 instance? Right now I'm exploring in d8 but > I can't seem to get into idle closures, for instance. > > On Sat, May 14, 2011 at 5:01 AM, Mikhail Naganov <[email protected]> > wrote: >> >> Hi Marcel, >> >> We have a heap profiler in Chrome. There is a current version, which >> is turned on by default, it's pretty limited. >> To try an upcoming version with much better capabilities, do the >> following: >> - grab one of the latest continuous build versions of Chromium from >> here: >> http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html >> - open DevTools (wrench menu > Tools > Developer Tools) >> - go to "Profiles" page >> - type "leakz" (w/o quotes), a "congratulations" message should pop up >> - now you can take snapshots, explore and compare them. >> >> On Fri, May 13, 2011 at 12:51, 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
