Fix potential memory leak if zstd_compress fails #124
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
This PR fixes a potential memory leak in the compression path. In the current implementation, if zstd_compress returns an error, rb_raise is called immediately. If rb_raise will be called, the subsequent ZSTD_freeCCtx(ctx) is never reached. This change ensures that ZSTD_freeCCtx(ctx) is called before raising the exception, preventing the context leak. Seems zstd_compress errors are rare in practice, this fix ensures safety for those edge cases.
Contributor
Author
|
I found other memory leak. I will create other PR. |
Owner
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This PR fixes a potential memory leak in the compression path.
In the current implementation, if zstd_compress returns an error, rb_raise is called immediately. If rb_raise will be called, the subsequent ZSTD_freeCCtx(ctx) is never reached.
This change ensures that ZSTD_freeCCtx(ctx) is called before raising the exception, preventing the context leak. Seems zstd_compress errors are rare in practice, this fix ensures safety for those edge cases.