"Possible EventEmitter memory leak detected" by EventEmitter2

[baalexander]

I was finally able to reproduce this bug and figure out what was going on.

When a ROS message or service call is supposed to send to the server, it's actually deferred until a WebSocket connection is established. This is by design. However, if you try to send more than 10 messages or service calls to the server before a WebSocket connection has been established with rosbridge, then EventEmitter2 assumes it's a memory leak.

As queueing up via the connection event is by design and allows for easier code, I agree with the original proposal to setMaxListeners(0) so more than 10 requests can be queued up.

I'll fix this when I'm back in town next week unless someone needs it done earlier.

[rctoris]

👍

[baalexander]

Fixed with Pull Request #41.