Have you tried using a memory profiler ? If you can, run the code on this gist (https://gist.github.com/4073604). It will generate heapdumps that you can analyze later on chrome.
Luis -- On Fri, Jan 11, 2013 at 2:17 AM, Ket <kettin...@gmail.com> wrote: > Hi, > > I've an experience that my app eat up my web server memory and it stop > working. > > How do you release memory when the app is not in use and how do you manage > memory allotment so that node.js would not use up all the memory again and > again. > > 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 nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
