You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 26, 2021. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: