Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate EventEmitter memory leak warning #10

Open
yamalight opened this issue Mar 23, 2016 · 4 comments
Open

Investigate EventEmitter memory leak warning #10

yamalight opened this issue Mar 23, 2016 · 4 comments
Labels
Milestone

Comments

@yamalight
Copy link
Contributor

Trace from production:

(node) warning: possible EventEmitter memory leak detected. 11 unhandledRejection listeners added. Use emitter.setMaxListeners() to increase limit.
  at Pipe.channel.onread (internal/child_process.js:444:11)
  at process.addListener (events.js:252:17)
  at process.emit (events.js:185:7)
  at Pipe.channel.onread (internal/child_process.js:444:11)
  at handleMessage (internal/child_process.js:718:10)
  at emitTwo (events.js:100:13)
  at Pipe.channel.onread (internal/child_process.js:444:11)
  at process.addListener (events.js:252:17)
@yamalight yamalight added the bug label Mar 23, 2016
@yamalight yamalight added this to the Alpha 4 milestone Mar 23, 2016
@yamalight
Copy link
Contributor Author

Still happens (BBC world map use case) according to kibana logs:

(node) warning: possible EventEmitter memory leak detected. 11 unhandledRejection listeners added. Use emitter.setMaxListeners() to increase limit.
  at process.<anonymous> (runner.js:90:9)
  at handleMessage (internal/child_process.js:718:10)
  at Pipe.channel.onread (internal/child_process.js:444:11)

@yamalight yamalight reopened this Apr 12, 2016
@pke0108
Copy link

pke0108 commented May 30, 2017

@yamalight Any news on this issue ?

@yamalight
Copy link
Contributor Author

@PavanDevOps does this still happens with latest node? I believe it was a bug in one of the older node versions

@pke0108
Copy link

pke0108 commented Jun 5, 2017

@yamalight I dont see the error after restart.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants