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.

Sign up for GitHub

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

Jump to bottom

"EventEmitter memory leak detected" probably caused by repeated pipes to process.stdout #69

Open
jarnoharno opened this issue Jun 30, 2014 · 1 comment
Open

"EventEmitter memory leak detected" probably caused by repeated pipes to process.stdout #69

jarnoharno opened this issue Jun 30, 2014 · 1 comment
Labels
bug

Comments

@jarnoharno
Copy link

The warning (node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit. is probably caused by repeatedly creating pipes to process.stdout in containers.js. These temporary pipes should be unpiped when not needed anymore.
@jarnoharno jarnoharno added the bug label Jun 30, 2014
@lakka
Copy link

lakka commented Jul 1, 2014

When creating the container with conteiners.js the talkative parameter should be set to false when no logging is required. This will prevent containers.js from attaching pipes to containers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lakka @jarnoharno