Move a couple statics that are highly contended on solution load to just be class members as their container is a singleton.#12679
Merged
ToddGrun merged 1 commit intodotnet:mainfrom Jan 14, 2026
Conversation
…ust be class members as their container is a singleton.
davidwengier
approved these changes
Jan 14, 2026
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
2 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.
Looks like there is some concurrent invocation of this method that happens during solution load that is hitting some contention around static variable usage. As this is within a singleton MEF component, we can just move those static variables to be instance variables and remove this point of contention.
*** Before ***
*** After ***
