[dotnet] Avoid potential deadlock when starting new dev tools session#12592
Merged
jimevans merged 2 commits intoSeleniumHQ:trunkfrom Aug 30, 2023
nvborisenko:get-devtools-deadlock
Merged
[dotnet] Avoid potential deadlock when starting new dev tools session#12592jimevans merged 2 commits intoSeleniumHQ:trunkfrom nvborisenko:get-devtools-deadlock
jimevans merged 2 commits intoSeleniumHQ:trunkfrom
nvborisenko:get-devtools-deadlock
Conversation
Member
|
Does #12614 affect this? |
Member
Author
|
Should not, it's still actionable. |
8 tasks
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
4 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.
Description
There is a chance to get a deadlock when starting new cdp session.
Motivation and Context
Fixes #11703
Types of changes
Checklist
I have tested it locally, the issue is not reproducible anymore.