| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…ust have exclusive access
|
Tagging subscribers to this area: @dotnet/ncl |
Sorry, something went wrong.
There was a problem hiding this comment.
Looks like we could have used DisconnectResults directly, there was no need to put it into a variable - that is a cosmetic change.
The real meaningful change is protecting the dictionary from unlocked access - which happened in 2 places.
Sorry, something went wrong.
There was a problem hiding this comment.
I think it would would work even without using local variable disconnectResults however using it will not harm anything and could have slightly better runtime performance by not calling DisconnectResults getter multiple time.
Changes looks safe and correct to me.
Sorry, something went wrong.
|
It is worth fixing in servicing to unblock customers. Marking as such. |
Sorry, something went wrong.
The reason behind the local variable is that the getter results in a Volatile.Read. Which makes it more expensive. |
Sorry, something went wrong.
|
Approved by .NET Shiproom (@SteveMCarroll) over email on 1/8. Marking Servicing-approved. |
Sorry, something went wrong.
|
/ba-g failing flaky tests most probably unrelated to changes of this PR |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Backport of #107804 to release/9.0-staging
Fixes #107025
/cc @rokonec @pjannesen
Customer Impact
Reported by customer in #107025. Affects their admin access to services - causes reliability problem.
Regression
From .NET Framework
Testing
Note: The problem is intermittent and hard to reproduce.
Manual testing has been performed - customer validated with private patch prior to submitting .NET 10 PR - see #107025 (comment)
Risk
Low - these simple changes do not add or modify complex logic