Fix leak of listeners for process #432
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When I run `mocha --watch` and after 11th running, the following message was shown: ``` (node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit. ``` It seems that 'uncaughtException' listener is not released. Because, the listener to be released is different from listened one. To fix this issue, I gave the same listener to `process.on` and `process.removeListener`.
|
This issue has been inactive for over 2 months so I'm closing it. If you think it's still an issue re-open. - tjbot |
|
It does not fix yet. |
|
pushed the fix |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When I run
mocha --watchand after 11th running, the following message wasshown:
It seems that 'uncaughtException' listener is not released.
Because, the listener to be released is different from listened one.
To fix this issue, I gave the same listener to
process.onandprocess.removeListener.