one more bit of info, this is also leaking: _events in IncomingMessage @222955 incoming in HTTPParser @193799 530 in (Global handles) @27 parser in function() @222957 parser in CleartextStream @222953 parser in function() @242731 parser in function() @242719 parser in function serverSocketCloseListener() @242721 parser in function abortIncoming() @242725 parser in function() @254441 parser in function() @256331
On Thursday, November 15, 2012 4:05:41 PM UTC-5, marcucio wrote: > > I hope someone that is more familiar with nodejs can help point me int he > right direction. > > Background: > I have a https server that seems to be leaking memory. The profiler give > me the following information on the retained memory: > > This is what is leaking with every https request: > > headers in IncomingMessage @387013 > incoming in HTTPParser @73119 > 1109 in (Global handles) @27 > parser in function() @382505 > parser in CleartextStream @382491 > parser in function() @382503 > parser in function() @382489 > parser in function serverSocketCloseListener() @382493 > parser in function abortIncoming() @382497 > parser in function() @397821 > parser in function() @410755 > > I think this is internal to nodejs, where should I look at to see what is > holding on to this memory? Any suggestions or direction would be > appreciated. > -- 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
