Skip to content
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

MaxListenersExceededWarning when running many watches #59

Closed
dobesv opened this issue Oct 31, 2018 · 3 comments
Closed

MaxListenersExceededWarning when running many watches #59

dobesv opened this issue Oct 31, 2018 · 3 comments

Comments

@dobesv
Copy link

dobesv commented Oct 31, 2018

I run a handful of watches and I get these warnings:

(node:15779) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 unpipe listeners added. Use emitter.setMaxListeners() to increase limit
(node:15779) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 drain listeners added. Use emitter.setMaxListeners() to increase limit
(node:15779) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:15779) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added. Use emitter.setMaxListeners() to increase limit
(node:15779) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 finish listeners added. Use emitter.setMaxListeners() to increase limit
(node:15779) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 unpipe listeners added. Use emitter.setMaxListeners() to increase limit
(node:15779) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 drain listeners added. Use emitter.setMaxListeners() to increase limit
(node:15779) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:15779) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added. Use emitter.setMaxListeners() to increase limit
(node:15779) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 finish listeners added. Use emitter.setMaxListeners() to increase limit

When this happens, it doesn't seem to detect changes to files. It's possible this is actually a nodemon issue.

@dobesv
Copy link
Author

dobesv commented Oct 31, 2018

Upgrading nodemon seems to have helped in terms of detecting changes. However, it still prints these warnings prior to launching any nodemon process. Maybe just need to call emitter.setMaxListeners() somewhere?

To reproduce, just set up a bunch of watch configs.

@M-Zuber
Copy link
Owner

M-Zuber commented Jan 23, 2019

🤔 I would rather not call setMaxListeners by default.

I will look into adding an option in the config

@M-Zuber
Copy link
Owner

M-Zuber commented Jun 13, 2021

see #81, there is a release coming soon that will allow this setting

@M-Zuber M-Zuber closed this as completed Jun 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants