I'm also interested in this. JavaScript seems to be an easy place to leave memory open.
This article looks interesting https://github.com/felixge/node-memory-leak-tutorial. It's pretty dumb, but using a debugger attached to Chrome, you can see the size and count of objects in memory. Its a very simple way to see if something is ballooning. Seb. -- 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
