This repository was archived by the owner on Jan 24, 2024. It is now read-only.
Fix Netty buffer / direct memory leak in MessageFetchContext - #1069
Merged
BewareMyPower merged 1 commit intoFeb 11, 2022
Merged
Conversation
lhotari
commented
Feb 11, 2022
lhotari
commented
Member
- Fix thread safety issue for MessageFetchContext #1049 changed behavior, therefore this change is needed
- streamnative#1049 changed behavior, therefore this change is needed
|
|
BewareMyPower
approved these changes
Feb 11, 2022
Contributor
|
I confirm that this fix resolves the memory I was investigating |
Demogorgon314
approved these changes
Feb 11, 2022
BewareMyPower
pushed a commit
that referenced
this pull request
Feb 11, 2022
BewareMyPower
pushed a commit
that referenced
this pull request
Feb 11, 2022
BewareMyPower
pushed a commit
that referenced
this pull request
Feb 11, 2022
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
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.