Skip to content
This repository has been archived by the owner on Feb 26, 2021. It is now read-only.

Possible EventEmitter memory leak detected bug in Rendezvous #58

Open
patientplatypus opened this issue Sep 3, 2018 · 1 comment
Open
Labels

Comments

@patientplatypus
Copy link

So, I don't really know how to debug this and I find it pretty frustrating. The rendezvous server that is mentioned here hits memory leaks when developing on localhost - this makes me incredibly uncertain about deploying this to production.

patientplatypus:~/Documents/zennify.me/backend:14:25:57$rendezvous --port=9090 --host=127.0.0.1
Listening on: http://127.0.0.1:9090
(node:64740) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 disconnect listeners added. Use emitter.setMaxListeners() to increase limit
(node:64740) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 disconnect listeners added. Use emitter.setMaxListeners() to increase limit

What is the solution to this? If it's as simple as changing something in the Rendezvous server code, can we do that? Is there a node setting I have to toggle (I don't know whether setting maxListeners actually solves the problem or kicks the can)? I haven't actually seen this sort of error before and I'm uncertain as to how to debug.

@mkg20001
Copy link
Member

mkg20001 commented Sep 4, 2018

We're aware of this bug and have no idea how to fix it either. If you manage to fix it, that would be really awesome

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants