-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On Install: (node:13734) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. #29
Comments
When I try to start the Magic mirror with this plugin activated, I get the following Error message in terminal:
This messages appears multiple (10+) times and then the start script hangs until I send a SIGKILL with ctrl-c: No mirror display appears. I hope this helps and it's not me who makes a stupid beginner's error here, but AFAIR I did follow the MM-documentation and this readme carefully. deactivating the plugin in config.js for now, but ready to help debugging when instructed ;-) |
Hello @DamageIncorporated , thats a really strange error message, especially because the file name Could you provide me with more informations of your setup? I cannot reproduce that issue, so the following information would be useful:
Thanks! |
Hey, I had the same problem. It's a bit silly that with pm2 you only ever see the last 15 lines in the log. I looked at the entire log and found the following error:
I took a closer look and the only problem is that the request library is not installed. So I made an |
I don't know if this is a serious issue, but I saw it during installation of the module and to be safe, I post it anyway:
The following message appears multiple (10+) times in the terminal while running
npm install
:(node:13734) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit
after that, the install seems to finish okay.
Now I'll try to configure it in my new MM² smart display and see if it works ;-)
The text was updated successfully, but these errors were encountered: