-
Notifications
You must be signed in to change notification settings - Fork 293
Console.log bug: MaxListenersExceededWarning #1876
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
Comments
Ditto, on Node.js v12.0.0. |
I don't know why this issue was moved there. It's a bug report, not an help request. |
@Zoddo - can you please share your test case? |
As said, I'm not able to produce a simple test case (this bug is probably triggered under specific conditions). But the EventEmitter generating this error is internal to node (just take a look at the stack trace). Maybe @ollisal can have more chances than me, and provide a test case. |
Had the same issue when i was using |
I'm getting this issue on OSX
|
@Zoddo , is this still an issue? |
inactive, closing |
I got this error:
I was not able to produce a simple script that reproduce this error (I don't know exactly which condition trigger this bug), but I'm able to reproduce it anytime in my code.
From what I can see on the stacktrace, the EventEmitter instance which produce this warning is internal to node. The listeners seem to be registered during a
console.log()
call.The text was updated successfully, but these errors were encountered: