node event listener warning about node-dbus-next HOT 6 CLOSED

thanks for the quick answer :)
the warning i get is

MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 {"path":"/org/bluez/hci0/dev_XX_XX_XX_XX_XX_XX/player0","interface":"org.freedesktop.DBus.Properties","member":"PropertiesChanged"} listeners added. Use emitter.setMaxListeners() to increase limit

i think that this warn is thrown because of the listeners added to get the "properties-changed" events inside _initXml inside proxy-object.js file , is that possible?
at now i haven't a test case, ill try to make one and post it when i can
thanks again!

from node-dbus-next.

There's probably a memory leak somewhere in the library. I've gotten this warning as well. I never tested the case where objects come and go in a loop because that's not what I was doing with it.

I would like to see this fixed. It would help if you could post the warnings you are getting and a minimal test case to show the bug.

If you want to look into the library and see what's going on that would be helpful as well.

from node-dbus-next.

hello , i've modified the proxy-object file and add a new method to it , give it a try when you can

call this method when you don't need anymore a proxy object (it free the internal listeners).
using this method before destroy the proxy-object made the memory leak gone in my app

from node-dbus-next.

i've modified the function removeAllEventListeners , we can call this function when we are destroyng a proxy obj in order to release ALL the listeners for _signals , you are rigth, that's a better behaviour

from node-dbus-next.

@leonardo-k can you look at bd08f64 and see if latest master fixes your issue without #30?

from node-dbus-next.

I believe this is resolved by that commit.

from node-dbus-next.