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