EventEmitter memory leak detected

164 views
Skip to first unread message

Kevin Systrom

unread,
Feb 24, 2011, 5:20:53 PM2/24/11
to Socket.IO
I've seen on the board you've addressed this very warning a bunch of
times... but it seems like it got fixed in the past. We've got a new
site up using your stuff http//demo.instagram.com and we're seeing
10-15 req/sec and every now and then it seems to poop out with the
following warning:

(node) warning: possible EventEmitter memory leak detected. 11
listeners added. Use emitter.setMaxListeners() to increase limit.
Trace:
at Socket.<anonymous> (events.js:101:17)
at [object Object].<anonymous> (/usr/local/lib/node/.npm/socket.io/
0.6.12/package/lib/socket.io/client.js:70:19)
at [object Object]._onConnect (/usr/local/lib/node/.npm/socket.io/
0.6.12/package/lib/socket.io/transports/xhr-polling.js:23:35)
at [object Object].check (/usr/local/lib/node/.npm/socket.io/
0.6.12/package/lib/socket.io/listener.js:77:12)
at Server.<anonymous> (/usr/local/lib/node/.npm/socket.io/0.6.12/
package/lib/socket.io/listener.js:33:14)
at Server.emit (events.js:45:17)
at HTTPParser.onIncoming (http.js:1078:12)
at HTTPParser.onHeadersComplete (http.js:87:31)
at Socket.ondata (http.js:977:22)
at Socket._onReadable (net.js:654:27)


Our code for the server is open source, so if you're curious to have a
look: http://github.com/Instagram/Realtime-Demo

If there's any other data I can provide to help debug, I'd gladly do
it. Thanks for the socket.io stuff -- very cool.

Kevin

Truong Nguyen

unread,
Feb 28, 2011, 1:05:04 PM2/28/11
to sock...@googlegroups.com
Issued confirmed, I have it too.

Guillermo Rauch

unread,
Feb 28, 2011, 1:07:54 PM2/28/11
to sock...@googlegroups.com
This affects only the XHR transports. It's not really a memory leak because upon a full disconnect the connection gets cleared,
but I'm going to fix it regardless.

--
Guillermo Rauch
http://devthought.com

RobKohr

unread,
Apr 5, 2011, 7:19:29 PM4/5/11
to Socket.IO
Seems like this was fixed here
https://github.com/LearnBoost/Socket.IO-node/pull/161
and merged on 3/30/2011

Thanks!

RobKohr

unread,
Apr 5, 2011, 7:14:04 PM4/5/11
to Socket.IO
Any update on this, I am still receiving this error for XHR
transports.

On Feb 28, 11:07 am, Guillermo Rauch <rau...@gmail.com> wrote:

Arnout Kazemier

unread,
Apr 6, 2011, 2:57:20 AM4/6/11
to sock...@googlegroups.com
Are you using the latest version? 0.6.17 is the latest release

---
Arnout Kazemier

☠ JavaScript Pirate, Arrghh matey ☠

Reply all
Reply to author
Forward
0 new messages