Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Warning] MaxListenersExceededWarning: Possible EventEmitter memory leak detected

See original GitHub issue

Describe the bug

As seen in this log at line time 3:16:09 PM:

(node:1262) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 data listeners added to [Socket]. Use emitter.setMaxListeners() to increase limit

Steps to reproduce

Running my infamous debug repo 😃

Expected behavior

Everything runs just fine. Wanted to give a heads up in the case this is not expected, so you can take a look at it.

Configuration

I did bump node from 10 to 12 to see if the warning was still there, just in case.

Screenshots

If applicable, add screenshots to help explain your problem.

Issue Analytics

State:
Created 4 years ago
Comments:8 (5 by maintainers)

Top GitHub Comments

2reactions

ehmickycommented, Mar 4, 2020

I am looking into this issue but debugging it is currently hard because of implementation details summarized in #878. Thanks for following up!

1reaction

ehmickycommented, Mar 4, 2020

@talves I can reproduce the bug even with the latest version.

If you regenerate the yarn.lock, you should get the latest @netlify/build (0.1.80 as I write this). @netlify/cli uses the following semver range: "@netlify/build": "^0.1.7". But your yarn.lock might hold this up.

Top Results From Across the Web

possible EventEmitter memory leak detected - node.js

I'd like to point out here that that warning is there for a reason and there's a good chance the right fix is...

(node:30) MaxListenersExceededWarning: Possible ... - GitHub

(node:30) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added. Use emitter.setMaxListeners() to increase limit ...

How to fix possible EventEmitter memory leak detected - cri.dev

The warning possible EventEmitter memory leak detected happens when you have more than 10 listeners (read EventEmitter) attached to an event ...

Possible EventEmitter memory leak detected. 11 scanStop ...

The node red console indicates "MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 scanStop listeners added. Use emitter.

Understanding memory leaks in node.js part 2 - alxolr

(node:10031) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. Eleven event listeners added. Use emitter.