Inspect the memory usage of your process. If the RSS is going up then periodically take core dumps and inspect them in mdb. ( http://dtrace.org/blogs/bmc/2012/05/05/debugging-node-js-memory-leaks/ )
Alternatively take heapdumps ( https://github.com/bnoordhuis/node-heapdump ) and inspect them in Chrome's profiler. Failing that install a REPL in your application and expose known tokens that might leak like server and inspect them at run time to see whether there is a leak. And lastly just do a Gedanken experiment. Look at your code and think hard. Of course the above are for production. If you can reproduce the memory leak locally then simply isolate it and use the debugger locally to figure out what's going on. Even excessive console.log printing should help identify the leak. On Sun, Dec 2, 2012 at 4:32 AM, 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
