I have now had to implement a temporary 'fix' for this problem but I think it highlights exactly where the problem is.
When the memory usage gets over 30mb I terminate and restart the connection created with net.createConnection. This clears all of the hidden memory loss. I think that this proves that this is a genuine leak in the node code as opposed to anything done in the application. -- 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
