Add lock on _checkRegistry operations #11361
Draft
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.
Fixes #11319
Context
It looks like the environment modifies
_checkRegistry
concurrently due to throttling logicmsbuild/src/Build/BuildCheck/Infrastructure/BuildCheckManagerProvider.cs
Line 373 in 4042363
and
msbuild/src/Build/BuildCheck/Infrastructure/BuildCheckManagerProvider.cs
Line 380 in 4042363
In
RemoveChecksAfterExecutedActions
the code is processing throttled checks andRemoveCheck
method is modifying the_checkRegistry
while theFindAll
loop is still iterating over it.Changes Made
add lock for the
_checkRegistry
operations to avoid issues with synchronization.