Hi Aivis, I had some luck with this instructions: https://gist.github.com/4073604
The idea is to generate heapdumps periodically and then analyse them with Chrome's profiler. You'll have to be patient to detect the actual object that's leaking, but that's it. Good luck, Luis Luis -- On Sun, Dec 2, 2012 at 12:32 PM, Aivis Siliņš <[email protected]>wrote: > How do you detect memory leaks? > > - v8-profiler is broken (also all other modmodules who use v8-profiler...) > - dtrace does not work in linux > - nodetime provide only 20 min. for free... > > Thank you. > > -- > 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 > -- 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
