possible memory leak

[crcastle]

Found the below exception stack trace in the log today:

(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace:
at Socket. (events.js:123:17)
at [object Object]. (/home/keg/keg.io/lib/Socket.IO-node/lib/socket.io/client.js:70:19)
at [object Object]._onConnect (/home/keg/keg.io/lib/Socket.IO-node/lib/socket.io/transports/xhr-polling.js:23:35)
at [object Object].check (/home/keg/keg.io/lib/Socket.IO-node/lib/socket.io/listener.js:77:12)
at Server. (/home/keg/keg.io/lib/Socket.IO-node/lib/socket.io/listener.js:33:14)
at Server.emit (events.js:67:17)
at HTTPParser.onIncoming (http.js:1109:12)
at HTTPParser.onHeadersComplete (http.js:108:31)
at Socket.ondata (http.js:1008:22)
at Socket._onReadable (net.js:682:27)

[dcarney]

Is this using the latest socket.io code? From my cursory research on the Googles, it looks like this issue might be fixed in the latest socket.io?

[crcastle]

IE's error dialog didn't say anything about the socket.io js file, but
I guess that doesn't mean much. But also I thought socket.io worked on
IE. It has several fall back mechanisms. Not sure if we're using the
most recent version.

On May 18, 2011, at 11:20 PM, dcarney
[email protected]
wrote:

Is this using the latest socket.io code? From my cursory research on the Googles, it looks like this issue might be fixed in the latest socket.io?

Reply to this email directly or view it on GitHub:
#17 (comment)

[crcastle]

i have not seen this in a month or so. closing this issue

[crcastle]

Seeing this issue again. I'm going to see if updating socket-io library fixes this.