Add a test to demonstrate connection logical deadlock due assigning capacity to pending open streams #863
+219
−0
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.
This is a companion PR to help understand the bug pointed out by PR #860.
The program I present here is based on PR #852, which also demonstrates a deadlock. However, according to my research, these two examples deadlock for entirely different reasons. While PR #852 deadlocks due to not calling flow capacity methods, the program I present here DOES, afaik, correctly call flow capacity methods.
The test presented here sends requests and responses in chunks, and due to that, triggers a deadlock because the client ends up assigning stream capacity to streams that are still in the pending_open state. Once the client assigns all of the connection capacity to streams that are in pending_open, the entire program deadlocks as nothing can make progress.
The deadlock in this program is fixed by PR #860.