After a new deployment of a VSIX, first test run randomly hangs VS #34
Labels
Comments
kzu
added a commit
that referenced
this issue
Aug 23, 2022
This can hang VS if the cache is being rebuilt and we're requesting it synchronourly. Fixes #34
kzu
added a commit
that referenced
this issue
Aug 23, 2022
This can hang VS if the cache is being rebuilt and we're requesting it synchronourly. Fixes #34
kzu
added a commit
that referenced
this issue
Aug 23, 2022
This can hang VS if the cache is being rebuilt and we're requesting it synchronourly. Fixes #34
kzu
added a commit
that referenced
this issue
Aug 23, 2022
Otherwise, the previous approach can hang VS if the cache is being rebuilt and we're requesting it synchronously from within the process start. Note that unless MEF components are requested, we don't even initialize the component model service at all either. Fixes #34
kzu
added a commit
that referenced
this issue
Aug 23, 2022
Otherwise, the previous approach can hang VS if the cache is being rebuilt and we're requesting it synchronously from within the process start. Note that unless MEF components are requested, we don't even initialize the component model service at all either. Fixes #34
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From an actual hang dump, the culprit is the
GetService<SComponentModel>, which doesn't seem like xunit.vsix should be forcing.The text was updated successfully, but these errors were encountered: