Handle a leak when thrift requests are aborted early #5535
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:
We received a report where thrift was leaking pooled byte buffers.
We use pooled byte buffers to create the thrift request in
THttpClientDelegate
assumingthat it will be released when sent on the wire for normal cases.
armeria/thrift/thrift0.13/src/main/java/com/linecorp/armeria/internal/client/thrift/THttpClientDelegate.java
Line 134 in 7f30250
However, if any requests don't have a chance to reach the wire, they will leak the byte buffer.
I believe it is reasonable to assume that requests not decoded properly should be cleaned up. Hence, I propose we do an extra
req.abort
insidehandlePreDecodeException
.Modifications:
handlePreDecodeException
to accept an additionalHttpRequest
parameterResult: