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.

MaxListenersExceededWarning

See original GitHub issue

Version

3.9.3

Environment info

  System:
    OS: macOS 10.14.5
    CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
  Binaries:
    Node: 11.9.0 - /usr/local/bin/node
    Yarn: 1.13.0 - /usr/local/bin/yarn
    npm: 6.5.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 75.0.3770.142
    Firefox: 68.0
    Safari: 12.1.1
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce

run vue ui from terminal
switch projects a few times with dropdown (not always, but frequently)
check terminal

What is expected?

No errors

What is actually happening?

$ vue ui
🚀  Starting GUI...
🌠  Ready on http://localhost:8000
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 exit listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGABRT listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGALRM listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGHUP listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGTERM listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGVTALRM listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGXCPU listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGXFSZ listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGUSR2 listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGTRAP listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGSYS listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGQUIT listeners added. Use emitter.setMaxListeners() to increase limit
(node:43039) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGIOT listeners added. Use emitter.setMaxListeners() to increase limit

I’m occasionally losing hot reloading and this is the only thing that seems relevant

Issue Analytics

State:
Created 4 years ago
Comments:5

Top GitHub Comments

2reactions

karol-fcommented, Aug 1, 2019

Seems like you have large number of files in your repository. I suggest checking if there’s not folder with large number of files that can be move elsewhere (e.g. to node_modules) or change node max listeners limit.

0reactions

sertacocommented, Aug 4, 2020

somehow this does increase my listeners.

Top Results From Across the Web

Possible EventEmitter memory leak detected. 11 message lis ...

MaxListenersExceededWarning : Possible EventEmitter memory leak detected. 11 message lis teners added. Use emitter.setMaxListeners() to increase ...

Possible EventEmitter memory leak detected. 11 ... - GitHub

Describe the bug When using simple cache adapters MaxListenersExceededWarning is emitted. This has previously been investigated in #792 and #1128 but either ...

Actions execution throws "MaxListenersExceededWarning"

This error is a warning that is related to some of the necessary wrapping business logic for Actions and should not have any...

Possible EventEmitter memory leak detected. 11 scanStop ...

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

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

How to fix possible EventEmitter memory leak detected Published on 2020-07-16 <a rel="category" ì href="/tags/nodejs/" ...