On 19 March 2012 14:09, Nico Kaiser <[email protected]> wrote: > How can I debug this behavior? I tried node-inspector, but v8-profiler only > works with Node 0.4. Running node-gc every few seconds smoothes the memory > curve, but does not help anything.
If you did read the list, you would come across the same issue being discussed in this post: https://groups.google.com/d/msg/nodejs/Aq9BId5Tff8/7G3JxaIVd2YJ https://github.com/Jimbly/node-mtrace > I observed that process.memoryUsage().heapTotal stays at an acceptable level > (about 150 MB), only rss grows until the process gets killed. Does this tell > anything, e.g. Buffer leak? (I know the WebSocket modules use lots of small > buffers, but they should get freed, shouldn't they?). > > > Do you have any hint where I can look for leaks? > > Thanks, > Nico > > -- > 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
