I get a similar issue using socket.io with WEBSOCKET transport enabled. It also appear that RSS grows to fill up available memory but doesn't seem to hit an OOM. It just stays at a very high memory usage. On a 2gig machine it climbs to like 1960mb and is quite scary.
I've tried node up to 0.8.9 and still happens. On Friday, September 14, 2012 8:52:23 AM UTC-5, Tristan Slominski wrote: > > Having similar issue to what Nico is seeing... > > (a not very helpful picture follows): > the blue is RSS growing to fill up available memory, while the tiny pink > and red lines are the heapTotal and heapUsed, which stays bounded (around > 20-25 MB heap total in my case), data from 0.8.8 (haven't tried 0.8.9 yet) > > > https://plus.google.com/u/0/photos/106160293361349494652/albums/5787976828393231153/5787976827897869394 > > the common thread for me with Nico is that connections are constantly > created and destroyed. I've seen this behavior both using https connections > and then using only tls connections. > > On Thursday, September 13, 2012 10:25:03 AM UTC-5, Nico Kaiser wrote: >> >> >> Am 13.09.2012 um 10:05 schrieb Stefan Zehe <s.z...@upjers.com>: >> >> > 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. >> >> I'll check if I can get information about the _events arrays, but as I >> wrote before, 0.8.8 did not change much: >> >> http://cl.ly/image/2Y3N3w0t1I34 >> >> >> 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 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
