Abort signal - Possible EventEmitter memory leak detected. 11 abort listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit
See original GitHub issueWhen using abort signal with the esc client I get the following:
Possible EventEmitter memory leak detected. 11 abort listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit
Is esc or maybe undici missing to release the abort signal handler?
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:5
Top Results From Across the Web
MaxListenersExceededWarning and EventTarget #36423
11 testEvent listeners added to EventTarget. Use events.setMaxListeners() to increase limit . There is no setMaxListeners on EventTarget.
Read more >NodeJS : How to debug "EventEmitter memory leak detected ...
I have an EventEmitter to send a "stop signal" when stop() is called, which kills a process (video player). Problem was if I...
Read more >Node.js sends warnings when you add too many listeners to ...
... Possible EventEmitter memory leak detected. 11 event listeners added. Use emitter.setMaxListeners() to increase limit.
Read more >[NODE-2123] MaxListenersExceededWarning caused by ...
11 topologyDescriptionChanged listeners added. Use ... setMaxListeners() to increase limit ... Possible EventEmitter memory leak detected.
Read more >Too much audio input data? - Report bugs - Edge Impulse forum
(node:18) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 change listeners added to [StatWatcher]. Use emitter.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Getting this warning too 👍
Estou recebendo o mesmo aviso aqui também.
Não sei se essa issue pode ajudar em algo: https://github.com/node-fetch/node-fetch/issues/1295