Fix byteBuf potential memory leak problem. #3525
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
shoothzj
approved these changes
Oct 12, 2022
dlg99
approved these changes
Oct 12, 2022
zymap
approved these changes
Oct 13, 2022
|
@horizonzy Great job! Would you please create a separate PR for branch-4.14? |
zymap
pushed a commit
that referenced
this pull request
Oct 26, 2022
* Fix byteBuf potential memory leak problem. (cherry picked from commit 6215536)
Ghatage
pushed a commit
to sijie/bookkeeper
that referenced
this pull request
Jul 12, 2024
* Fix byteBuf potential memory leak problem.
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.
Descriptions of the changes in this PR:
If we don't flush the ReadResponse, the ByteBuf won't be released.