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.
EventEmitter memory leak detected
See original GitHub issueName of Issue
Description of Issue
somtimes error EventEmitter memory leak detected
- ActionHero Version:
15.0.2 - Node.js Version:
4.5.0 - Operating System
Windows 10
somtimes my actionhero server error EventEmitter memory leak detected setMaxListeners is When should best Run?
here error log
2016-09-02T07:06:25.672Z - info: worker: started workerId=2
2016-09-02T07:06:26.186Z - info: worker: ended workerId=2
(node) warning: possible EventEmitter memory leak detected. 19 error listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
at Redis.addListener (events.js:239:17)
at connection.connect (myproject\node_modules\node-resque\lib\connection.js:86:14)
at queue.connect (myproject\node_modules\node-resque\lib\queue.js:25:19)
at worker.connect (myproject\node_modules\node-resque\lib\worker.js:54:20)
at multiWorker.startWorker (myproject\node_modules\node-resque\lib\multiWorker.js:67:10)
at Immediate._onImmediate (myproject\node_modules\node-resque\lib\multiWorker.js:165:12)
at processImmediate [as _immediateCallback] (timers.js:383:17)
2016-09-02T07:06:25.672Z - info: worker: started workerId=2
2016-09-02T07:06:26.186Z - info: worker: ended workerId=2
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:7 (5 by maintainers)
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...
Read more >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 ...
Read more >(node) warning: possible EventEmitter memory leak detected ...
(node) warning: possible EventEmitter memory leak detected. 11 connected listeners added. Use emitter.setMaxListeners() to increase limit.
Read more >Node.js sends warnings when you add too many listeners to ...
This warning helps you to prevent memory leaks. Node.js processes can run for ages and when you have a bug in your code...
Read more >Understanding memory leaks in node.js part 2 - alxolr
(node:10031) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. Eleven event listeners added. 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 Free
Top 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
node-resquev3.0.3 is published, which fixes this issue. Thanks for catching it!https://github.com/taskrabbit/node-resque/releases/tag/v3.0.3
@evantahler thank you~