I've created a new tool using memwatch library. Check it out here; https://github.com/azer/memdiff
On Tuesday, December 4, 2012 10:06:03 PM UTC-8, Raynos wrote: > > Yeah horrible to use locally. > > Locally you can just isolate the bug and hook up a debugger. > > > On Tue, Dec 4, 2012 at 9:10 PM, mscdex <[email protected] <javascript:>>wrote: > >> On Dec 4, 10:44 pm, Jake Verbaten <[email protected]> wrote: >> > Yes. >> > >> > You should probably run your production node apps on joyent. >> >> Not really an option for me for what I'm doing. Also, SmartOS is not >> user friendly enough (from my experience) to use locally to try and >> fix memory leaks :-\ >> >> -- >> Job Board: http://jobs.nodejs.org/ >> Posting guidelines: >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> You received this message because you are subscribed to the Google >> Groups "nodejs" group. >> To post to this group, send email to [email protected]<javascript:> >> To unsubscribe from this group, send email to >> [email protected] <javascript:> >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en >> > > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
