Memory leak in EndPoint channels bugfix #2111
Merged
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
|
|
AqlaSolutions
force-pushed
the
feature/2110_memory_leak_bugfix
branch
2 times, most recently
from
41d14a2
to
c3ae63a
Compare
AqlaSolutions
force-pushed
the
feature/2110_memory_leak_bugfix
branch
from
c3ae63a
to
bbe5322
Compare
|
Awesome, many thanks! |
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.
Description
Solves #2110
Purpose
This pull request is a:
Checklist
According to our internal tests with this fix after 24 hours under load the memory snapshot doesn't contain the leaked objects anymore.