Fix EventEmitter leak #21
Merged
Conversation
This file contains hidden or 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
Signed-off-by: James Elias Sigurdarson <jamiees2@gmail.com>
jamiees2
force-pushed
the
fix-event-emitter-leak
branch
from
fa8f2cc to
bbb5658
Compare
github-actions bot
added a commit
that referenced
this pull request
Oct 7, 2021
Signed-off-by: James Elias Sigurdarson <jamiees2@gmail.com> 689870f
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
We were leaking event handlers by always attaching to the FluentSocket eventEmitter. When there is no error event but lots of timeouts, we end up attaching lots of error listeners and never removing them.
Fixes #20 I think