-
Notifications
You must be signed in to change notification settings - Fork 675
Fix NetworkWriter.AsyncFlushPages hanging FlushEvent waiters on send failure #1949
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
Open
hexonal
wants to merge
9
commits into
microsoft:main
Choose a base branch
from
hexonal:fix-networkwriter-flush-hang
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+101
−0
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
95b4698
Fix NetworkWriter.AsyncFlushPages hanging FlushEvent waiters on send …
hexonal 5859996
Harden regression test synchronization against review-flagged flakiness
hexonal fc44650
Merge branch 'main' into fix-networkwriter-flush-hang
hexonal d52bbc4
Remove residual race in AsyncFlushPages regression test synchronization
hexonal c4e561d
Merge remote-tracking branch 'origin/fix-networkwriter-flush-hang'
hexonal a1ca4cc
Merge branch 'main' into fix-networkwriter-flush-hang
hexonal 1effa03
Merge branch 'main' into fix-networkwriter-flush-hang
vazois feca0ec
Merge branch 'main' into fix-networkwriter-flush-hang
hexonal e4fb946
Merge branch 'main' into fix-networkwriter-flush-hang
hexonal 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
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.
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.
@hexonal, this seems serious. Can we guarantee that AsyncFlushPages does not decrement the value twice?
In the worst case, it might put the count into a state that creates the same issue that you were trying to resolve.
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.
I went through this carefully because it's a fair concern.
AsyncFlushPageCallbackdoesInterlocked.Decrement(ref result.count.count), and only signalsFlushEventonce that hits zero.Looking at
ClientTcpNetworkSender.SendResponse, every exception it can throw falls into one of two buckets: either it happens before theSocketAsyncEventArgsis even dispatched (throttle wait, checkout, buffer setup — no callback has run yet), orsocket.SendAsync()itself throws synchronously, which per the SAEA contract means the operation was never actually queued, soCompletedcan never fire for it afterward. IfSendAsyncsucceeds instead,SendResponsejust returns normally and the catch block never runs for that page at all.So there's no path where a page gets counted twice — the callback fires from exactly one place per page, either the normal completion or (only when the send never got queued) the new catch-block call, never both. I didn't just reason through this abstractly, I diffed the actual send path line by line against
mainto make sure I wasn't missing a partial-completion case.