-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
CTS.TryReset() concurrency issue #60182
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @mangod9 Issue DetailsDescriptionA full description of the issue is here: #60180 Reproduction Steps
Expected behavior
Actual behavior
Regression?No, Known WorkaroundsDo not use ConfigurationThe environment is not relevant. .NET SDK version is Other informationNo response
|
@stephentoub , I pushed draft PR but couldn't test it because of changes in CoreCLR codebase.
|
My bad, sorry. I changed target branch from |
@stephentoub , two PRs are here as discussed previously:
|
thanks! |
@stephentoub is there remaining 6.0 work here? or can we close now? |
No, #60323 should have closed it. Not sure why it didn't; maybe that bot doesn't have perms to do so. |
Description
A full description of the issue is here: #60180
Reproduction Steps
CancelAfter
with very small timeout (1-10 milliseconds)TryReset
concurrently withCancelAfter
Expected behavior
TryReset
should normally handle the concurrency with timer cancellation and return true/false.Actual behavior
Regression?
No,
TryReset
is introduced in .NET 6.Known Workarounds
Do not use
TryReset
at all and re-create CTS every time when needed.or
catch
ObjectDisposedException
by the caller:Configuration
The environment is not relevant. .NET SDK version is
6.0.100-rc.1.21458.32
Other information
No response
The text was updated successfully, but these errors were encountered: