# Memory leak message
**URL:** https://discourse.nodered.org/t/memory-leak-message/5277
**Category:** General
**Created:** [28 November 2018 19:50 UTC](https://discourse.nodered.org/t/memory-leak-message/5277 "2018-11-28T19:50:35Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@JoseGodinho](https://discourse.nodered.org/u/JoseGodinho)
#### Post date: [28 November 2018 19:50 UTC](https://discourse.nodered.org/t/memory-leak-message/5277/1 "2018-11-28T19:50:35Z")
Hello All
In order to help me identify what are the node that create the memory leak what is this (node:24366) in the list bellow? how can i find this bad guy?
(node:24366) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 open listeners added. Use emitter.setMaxListeners() to increase limit
(node:24366) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [28 November 2018 21:07 UTC](https://discourse.nodered.org/t/memory-leak-message/5277/2 "2018-11-28T21:07:28Z")
Is there a message in the debug pane? If so you can use the Search feature to search for the node id in the message in the debug pane.
---
### Author:  [@JoseGodinho](https://discourse.nodered.org/u/JoseGodinho)
#### Post date: [28 November 2018 21:09 UTC](https://discourse.nodered.org/t/memory-leak-message/5277/3 "2018-11-28T21:09:29Z")
Colin
No this message ins only in the node-red-log. And this node may be from node.js and not from the node-red
JLG
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [28 November 2018 23:12 UTC](https://discourse.nodered.org/t/memory-leak-message/5277/4 "2018-11-28T23:12:06Z")
This is an error from nodejs itself, so can't tell from that what is causing it. It's a warning rather than an error though so not a big problem while we figure it out..
One of the nodes you have added is probably not handling redeploys correctly and is adding another listener for inputs each time you deeply. (Is usually the problem)
---
### Author:  [@shrickus](https://discourse.nodered.org/u/shrickus)
#### Post date: [28 November 2018 23:37 UTC](https://discourse.nodered.org/t/memory-leak-message/5277/5 "2018-11-28T23:37:39Z")
> [@dceejay](#):
>
> One of the nodes you have added is probably not handling redeploys correctly
Or, there actually _are_ 11 clients listening... isn't there a setting that allows you to bump up that warning threshold?
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [29 November 2018 07:18 UTC](https://discourse.nodered.org/t/memory-leak-message/5277/6 "2018-11-29T07:18:35Z")
True, but only inside the node in question . whichever that is...