-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
More than 10 containers triggers EventEmitter memory leak warning #213
Labels
Comments
So solution is just to rise maximum of the listeners? |
Yeah, at least for my scenario. The "real" solution was to rewrite my code to not have 10 containers in one logger instance. |
Related to #327 |
indexzero
added a commit
that referenced
this issue
Jun 9, 2015
Suggested fix for #213: More than 10 containers triggers EventEmitter…
indexzero
added a commit
that referenced
this issue
Sep 25, 2015
Fixed in 44564de |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you create more than 10 containers, node's EventEmitter spews a warning about a possible memory leak.
I forked the project and added a test that demonstrates the problem (the test doesn't fail, but you should see the warning): https://github.com/BryanDonovan/winston/tree/max-listeners
My hacky solution is to add maxListeners as an option to container.get():
The text was updated successfully, but these errors were encountered: