Prevent memory leak if HTTP/1.1 encoding fails #1610
Merged
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.
Motivation:
When
HttpObjectEncoder
encodes meta-data or trailers an error mayhappen, which will cause a leak of internal
ByteBuf
. It may happen ifany of the encoding object throw or if it tries to expand the size of
that internal
ByteBuf
without success.Modifications:
ByteBuf
in case of any failures;Result:
Internal
ByteBuf
does not leak in case of an error inHttpObjectEncoder
.