You can pinpoint the leak by writing stress tests. Don't wait days for the leak to show in production. Find which component causes it. Make a list of suspects. If it's an http server, start with simple requests. Does the memory go up? No? Maybe it's the db? Try a million read/writes. Did you find the component that leaks? Follow the chain of events, commenting out suspicious code and trying again until the leak disappears.
2012/3/16 robot1125 <[email protected]>: >> So, my general question, how do people go about debugging memory leaks >> in native code in node (or node itself)? > > You may find this interview with Brian Cantrill of Joyent interesting. > > http://www.infoq.com/interviews/operating-nodejs-production-bryan-cantrill > > He discusses some of the tools they use to debug node apps in > production at Joyent. Some of them require running under their > homebrew OS, but the discussion may give you some ideas. > > -- > 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
