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 }}
Repository navigation
Piping a simple program to stdout gives "MaxListenersExceededWarning: Possible EventEmitter memory leak detected when" #16767
@mscdex I'm also on linux and can reproduce. --trace-warnings solves it for me but when other users report a memleak or you get a hard to reproduce one it would be nice if a stack happened per default.
Activity
mscdex commentedon Nov 5, 2017
You mean
--trace-warnings?addaleax commentedon Nov 5, 2017
Fwiw, I couldn’t reproduce this with master or with v8.9.0… but yes,
--trace-warningsshould give a good hint at what’s going on.mscdex commentedon Nov 5, 2017
I'm also not able to reproduce this on Linux.
mcollina commentedon Nov 5, 2017
I think it's this block: https://github.com/nodejs/node/blob/master/lib/console.js#L81-L87.
What I think is happening is that there are a bunch of writes that are about to error, and we add a lot of
'error'in the meanwhile.mcollina commentedon Nov 5, 2017
I can reproduce it on Mac OS X, you just need to wait some seconds before hitting
qwithin less.mcollina commentedon Nov 5, 2017
My fix is working, I'll send a PR soon.
mafintosh commentedon Nov 5, 2017
@mscdex I'm also on linux and can reproduce.
--trace-warningssolves it for me but when other users report a memleak or you get a hard to reproduce one it would be nice if a stack happened per default.mafintosh commentedon Nov 8, 2017
Thanks for the quick turnaround everyone :)
console: avoid adding infinite error listeners
console: avoid adding infinite error listeners
console: avoid adding infinite error listeners