Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

netty: Eliminate buffer release when there is an error as caller still owns the buffer. #10537

Merged
merged 6 commits into from
Sep 15, 2023
4 changes: 0 additions & 4 deletions netty/src/main/java/io/grpc/netty/NettyAdaptiveCumulator.java
Original file line number Diff line number Diff line change
Expand Up @@ -210,10 +210,6 @@ static void mergeWithCompositeTail(
// the input and the new tail so that finally block can handles them properly.
composite.readerIndex(prevReader);
} finally {
// Input buffer was merged with the tail.
if (in != null) {
in.release();
}
// If new tail's ownership isn't transferred to the composite buf.
// Release it to prevent a leak.
if (newTail != null) {
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -537,7 +537,7 @@ public CompositeByteBuf addFlattenedComponents(boolean increaseWriterIndex,
} catch (UnsupportedOperationException actualError) {
assertSame(expectedError, actualError);
// Input must be released unless its ownership has been to the composite cumulation.
assertEquals(0, in.refCnt());
assertEquals(1, in.refCnt());
// Tail released
assertEquals(0, tail.refCnt());
// Composite cumulation is retained
Expand All @@ -546,6 +546,7 @@ public CompositeByteBuf addFlattenedComponents(boolean increaseWriterIndex,
assertEquals(0, compositeThrows.numComponents());
} finally {
compositeThrows.release();
in.release();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should keep it abovefail("Cumulator didn't throw");

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is expected the in the case of an error that the ownership remained with the calling method so it is this method's responsibility to do the release.

}
}

Expand Down Expand Up @@ -573,7 +574,7 @@ public CompositeByteBuf addFlattenedComponents(boolean increaseWriterIndex,
} catch (UnsupportedOperationException actualError) {
assertSame(expectedError, actualError);
// Input must be released unless its ownership has been to the composite cumulation.
assertEquals(0, in.refCnt());
assertEquals(1, in.refCnt());
// New buffer released
assertEquals(0, newTail.refCnt());
// Composite cumulation is retained
Expand All @@ -582,6 +583,7 @@ public CompositeByteBuf addFlattenedComponents(boolean increaseWriterIndex,
assertEquals(0, compositeRo.numComponents());
} finally {
compositeRo.release();
in.release();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should keep it abovefail("Cumulator didn't throw");

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to release when there is an error since the new paradigm is that only successes change ownership.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discussed IRL, we do want to move it, but to another place

}
}
}
Expand Down