i solved my problems with an update to 0.8.9.

in 0.8.3 there was a bugfix

> events: Fix memory leak from removeAllListeners (Nathan Rajlich)

which might caused a steady growing _events-array.

Am 12.09.2012 07:47, schrieb Stefan Zehe:
> Same problem here. Our app slowly increases the rss. and i could not
> find anything with node-webkit-agent :(
>
> Am 12.09.2012 02:58, schrieb wavded:
>> Nico did you have any luck in your debugging adventures?  My symptoms
>> seems to very closely match yours.  Was going to try mtrace.
>>
>> On Monday, March 19, 2012 11:52:34 AM UTC-5, Nico Kaiser wrote:
>>
>>     Thanks Ilya, I'll have a second look at node-mtrace. 
>>
>>     I tried this (as I did read the list ;-)), but it did not help
>>     much, and I hoped someone could identify a specific class of
>>     problems with my description (RSS grows, heap stays ok)...
>>
>>     Nico
>>
>>
>>
>>     Am Montag, 19. März 2012 16:06:38 UTC+1 schrieb Ilya Dmitrichenko:
>>
>>         On 19 March 2012 14:09, Nico Kaiser <ni...@kaiser.me
>>         <javascript:>> 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://groups.google.com/d/msg/nodejs/Aq9BId5Tff8/7G3JxaIVd2YJ>
>>
>>         https://github.com/Jimbly/node-mtrace
>>         <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
>>         <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
>>         nod...@googlegroups.com <javascript:>
>>         > To unsubscribe from this group, send email to
>>         > nodejs+un...@googlegroups.com <javascript:>
>>         > For more options, visit this group at
>>         > http://groups.google.com/group/nodejs?hl=en?hl=en
>>         <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

-- 
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

Reply via email to