-
Notifications
You must be signed in to change notification settings - Fork 4k
core: fix off-heap ByteBuf leak on RejectedExecutionException #12891
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
Closed
kannanjgithub
wants to merge
1
commit into
grpc:master
from
kannanjgithub:rejected-execution-free-up-message
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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 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 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 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 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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prior to this PR,
exceptionThrown(Status status)was only ever called insiderunInternal()ofHeadersRead,MessagesAvailable, andStreamOnReady. All three executed insidecallExecutor.execute(...), meaningexceptionThrown()ran strictly on the applicationcallExecutorthread. In fact, its javadoc explicitly relies on this:When
callExecutor.execute(...)throwsRejectedExecutionException,messagesAvailable()catches it on the transport thread and directly invokesexceptionThrown(status)on the transport thread.Because
private Status exceptionStatus;is notvolatile, writingexceptionStatus = statusfrom the transport thread introduces a potential data race whenif (exceptionStatus != null)is subsequently checked on the application thread (e.g., insideStreamClosed.runInternal()).Consider making
exceptionStatusvolatile to guarantee visibility across threads:And updating or clarifying the corresponding javadoc on
exceptionThrown()(May only be called from the application thread.) to reflect that it can now be invoked from the transport thread upon task rejection.