(node:125008) MaxListenersExceededWarning: Possible EventEmitter memory leak detected
Multi tool use
(node:125008) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 ready listeners added. Use emitter.setMaxListeners() to increase limit
How exactly do I increase the number of listener events? I've searched around and none of the methods I've tried have worked : (
javascript node.js discord.js
asked Nov 12 '18 at 17:59
Fahim DhaliFahim Dhali
1
add a comment |
(node:125008) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 ready listeners added. Use emitter.setMaxListeners() to increase limit
How exactly do I increase the number of listener events? I've searched around and none of the methods I've tried have worked : (
javascript node.js discord.js
asked Nov 12 '18 at 17:59
Fahim DhaliFahim Dhali
1
what did the method mentioned in the error you posted (emitter.setMaxListeners()) do when you called it? Also, how many events are you trying to listen to at once? What is it you are trying to do that you need to increase the limit?
– Claies
Nov 12 '18 at 18:01
1
See: stackoverflow.com/questions/50709059/…
– Mark Meyer
Nov 12 '18 at 18:01
add a comment |
(node:125008) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 ready listeners added. Use emitter.setMaxListeners() to increase limit
How exactly do I increase the number of listener events? I've searched around and none of the methods I've tried have worked : (
javascript node.js discord.js
asked Nov 12 '18 at 17:59
Fahim DhaliFahim Dhali
1
(node:125008) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 ready listeners added. Use emitter.setMaxListeners() to increase limit
How exactly do I increase the number of listener events? I've searched around and none of the methods I've tried have worked : (
javascript node.js discord.js
javascript node.js discord.js
asked Nov 12 '18 at 17:59
Fahim DhaliFahim Dhali
1
asked Nov 12 '18 at 17:59
Fahim DhaliFahim Dhali
1
asked Nov 12 '18 at 17:59
Fahim DhaliFahim Dhali
1
asked Nov 12 '18 at 17:59
Fahim DhaliFahim Dhali
1
asked Nov 12 '18 at 17:59
Fahim DhaliFahim Dhali
1
1
what did the method mentioned in the error you posted (emitter.setMaxListeners()) do when you called it? Also, how many events are you trying to listen to at once? What is it you are trying to do that you need to increase the limit?
– Claies
Nov 12 '18 at 18:01
1
See: stackoverflow.com/questions/50709059/…
– Mark Meyer
Nov 12 '18 at 18:01
add a comment |
what did the method mentioned in the error you posted (emitter.setMaxListeners()) do when you called it? Also, how many events are you trying to listen to at once? What is it you are trying to do that you need to increase the limit?
– Claies
Nov 12 '18 at 18:01
1
See: stackoverflow.com/questions/50709059/…
– Mark Meyer
Nov 12 '18 at 18:01
what did the method mentioned in the error you posted (
emitter.setMaxListeners()) do when you called it? Also, how many events are you trying to listen to at once? What is it you are trying to do that you need to increase the limit?– Claies
Nov 12 '18 at 18:01
what did the method mentioned in the error you posted (
emitter.setMaxListeners()) do when you called it? Also, how many events are you trying to listen to at once? What is it you are trying to do that you need to increase the limit?– Claies
Nov 12 '18 at 18:01
1
1
See: stackoverflow.com/questions/50709059/…
– Mark Meyer
Nov 12 '18 at 18:01
See: stackoverflow.com/questions/50709059/…
– Mark Meyer
Nov 12 '18 at 18:01
add a comment |
2 Answers
2
active
oldest
votes
11 ready listeners added
means you have 11 <Discord.client>.on('ready', <function>)
so node.js warns you because that uses a lot of memory. You probably have nested events somewhere so it makes 11 ready events.
answered Nov 15 '18 at 13:28
PLASMA chickenPLASMA chicken
8441616
add a comment |
This is explained in the manual: http://nodejs.org/docs/latest/api/events.html#events_emitter_setmaxlisteners_n
What version of Node is this? What other code do you have? That isn't normal behavior.
In short, its: process.setMaxListeners(0);
Also see: node.js - request - How to “emitter.setMaxListeners()”?
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 not increasing the limit but figuring out why you're adding so many listeners to the same event. Only increase the limit if you know why so many listeners are being added and are confident it's what you really want.
I found this page because I got this warning and in my case there was a bug in some code I was using that was turning the global object into an EventEmitter! I'd certainly advise against increasing the limit globally because you don't want these things to go unnoticed.
answered Nov 16 '18 at 10:14
Pritam JanaPritam Jana
10913
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53267660%2fnode125008-maxlistenersexceededwarning-possible-eventemitter-memory-leak-det%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
11 ready listeners added
means you have 11 <Discord.client>.on('ready', <function>)
so node.js warns you because that uses a lot of memory. You probably have nested events somewhere so it makes 11 ready events.
answered Nov 15 '18 at 13:28
PLASMA chickenPLASMA chicken
8441616
add a comment |
11 ready listeners added
means you have 11 <Discord.client>.on('ready', <function>)
so node.js warns you because that uses a lot of memory. You probably have nested events somewhere so it makes 11 ready events.
answered Nov 15 '18 at 13:28
PLASMA chickenPLASMA chicken
8441616
add a comment |
11 ready listeners added
means you have 11 <Discord.client>.on('ready', <function>)
so node.js warns you because that uses a lot of memory. You probably have nested events somewhere so it makes 11 ready events.
answered Nov 15 '18 at 13:28
PLASMA chickenPLASMA chicken
8441616
11 ready listeners added
means you have 11 <Discord.client>.on('ready', <function>)
so node.js warns you because that uses a lot of memory. You probably have nested events somewhere so it makes 11 ready events.
answered Nov 15 '18 at 13:28
PLASMA chickenPLASMA chicken
8441616
edited Nov 16 '18 at 9:51
answered Nov 15 '18 at 13:28
PLASMA chickenPLASMA chicken
8441616
answered Nov 15 '18 at 13:28
PLASMA chickenPLASMA chicken
8441616
answered Nov 15 '18 at 13:28
PLASMA chickenPLASMA chicken
8441616
8441616
add a comment |
add a comment |
This is explained in the manual: http://nodejs.org/docs/latest/api/events.html#events_emitter_setmaxlisteners_n
What version of Node is this? What other code do you have? That isn't normal behavior.
In short, its: process.setMaxListeners(0);
Also see: node.js - request - How to “emitter.setMaxListeners()”?
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 not increasing the limit but figuring out why you're adding so many listeners to the same event. Only increase the limit if you know why so many listeners are being added and are confident it's what you really want.
I found this page because I got this warning and in my case there was a bug in some code I was using that was turning the global object into an EventEmitter! I'd certainly advise against increasing the limit globally because you don't want these things to go unnoticed.
answered Nov 16 '18 at 10:14
Pritam JanaPritam Jana
10913
add a comment |
This is explained in the manual: http://nodejs.org/docs/latest/api/events.html#events_emitter_setmaxlisteners_n
What version of Node is this? What other code do you have? That isn't normal behavior.
In short, its: process.setMaxListeners(0);
Also see: node.js - request - How to “emitter.setMaxListeners()”?
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 not increasing the limit but figuring out why you're adding so many listeners to the same event. Only increase the limit if you know why so many listeners are being added and are confident it's what you really want.
I found this page because I got this warning and in my case there was a bug in some code I was using that was turning the global object into an EventEmitter! I'd certainly advise against increasing the limit globally because you don't want these things to go unnoticed.
answered Nov 16 '18 at 10:14
Pritam JanaPritam Jana
10913
add a comment |
This is explained in the manual: http://nodejs.org/docs/latest/api/events.html#events_emitter_setmaxlisteners_n
What version of Node is this? What other code do you have? That isn't normal behavior.
In short, its: process.setMaxListeners(0);
Also see: node.js - request - How to “emitter.setMaxListeners()”?
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 not increasing the limit but figuring out why you're adding so many listeners to the same event. Only increase the limit if you know why so many listeners are being added and are confident it's what you really want.
I found this page because I got this warning and in my case there was a bug in some code I was using that was turning the global object into an EventEmitter! I'd certainly advise against increasing the limit globally because you don't want these things to go unnoticed.
answered Nov 16 '18 at 10:14
Pritam JanaPritam Jana
10913
This is explained in the manual: http://nodejs.org/docs/latest/api/events.html#events_emitter_setmaxlisteners_n
What version of Node is this? What other code do you have? That isn't normal behavior.
In short, its: process.setMaxListeners(0);
Also see: node.js - request - How to “emitter.setMaxListeners()”?
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 not increasing the limit but figuring out why you're adding so many listeners to the same event. Only increase the limit if you know why so many listeners are being added and are confident it's what you really want.
I found this page because I got this warning and in my case there was a bug in some code I was using that was turning the global object into an EventEmitter! I'd certainly advise against increasing the limit globally because you don't want these things to go unnoticed.
answered Nov 16 '18 at 10:14
Pritam JanaPritam Jana
10913
answered Nov 16 '18 at 10:14
Pritam JanaPritam Jana
10913
answered Nov 16 '18 at 10:14
Pritam JanaPritam Jana
10913
answered Nov 16 '18 at 10:14
Pritam JanaPritam Jana
10913
10913
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53267660%2fnode125008-maxlistenersexceededwarning-possible-eventemitter-memory-leak-det%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
sdqUuBPqjYJrAqvtUHYJyZ
what did the method mentioned in the error you posted (
emitter.setMaxListeners()) do when you called it? Also, how many events are you trying to listen to at once? What is it you are trying to do that you need to increase the limit?– Claies
Nov 12 '18 at 18:01
1
See: stackoverflow.com/questions/50709059/…
– Mark Meyer
Nov 12 '18 at 18:01