EventEmitter memory leak detected about sharejs HOT 7 CLOSED

Yep, you can ignore that. Its a known bug in node-browserchannel, because of how I'm using event emitters. I'm pretty sure its fine, and I just need to call emitter.setMaxListeners() to increase the limit.

from sharejs.

I was toying with a simple sketching tool and I seem to be loosing data. It works fine locally but when deployed in a remote server some ops seem to get lost. Could this be the root of the issue ?

from sharejs.

No. The event emitter 'bug' is just that I'm attaching >10 listeners to an event, and thats usually a sign of something fishy going on.

Can you give more details about missing data? Which version are you using? Do you get the same problem with sharejs 0.5-pre?

from sharejs.

I'm using HEAD from GitHub master branch. Basically i'm appending text to a JSON object, in this case something like {id:"fdcd",d:"M100,100 L200,200"} where mouse movement events result in new path commands being inserted in "d".
I end up loosing some path commands. Will try to look further into this and give you some more details.

from sharejs.

That'd be great.

from sharejs.

Ok, stupid event looping. The receiver ended up resetting the "d" attribute that's why some commands were lost. Sorry about that. I'll close the issue since the EventEmitter warning is related to BrowserChannel.

from sharejs.

The eventemitter bug is now here:
josephg/node-browserchannel#8

from sharejs.