Repository navigation
Conversation
On Windows the completion handler can be invoked twice for the same read after EOF, which released the DataBuffer twice. Closes spring-projectsgh-37377 Signed-off-by: Kacper Rydzyński <rydzwr@gmail.com>
spring-projects-issues
added
the
status: waiting-for-triage
This branch has not been deployed
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
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.
On Windows, WindowsAsynchronousFileChannelImpl can call the completion
handler a second time for the same read after EOF, when the channel is
closed. ReadCompletionHandler then releases the same DataBuffer twice.
This adds a once-only flag to the read Attachment and sets DISPOSED
before closing the channel.
Closes gh-37377