You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Visual Studio: 2022 Community, 17.12.3 (and other recent versions)
This extension: 1.1.228
Description
Note: this only happens when the FCC extension is enabled. Only recourse is to kill the devenv.exe process. I usually give up waiting after some minutes. While I was gathering info for this bug report, I guess about 8-10 minutes passed and suddenly VS became response. Typically I have given up after 3-4 minutes :)
We have a monorepo with ~20 projects and 150k LoC.
DevEnv.exe is typically showing 'Not responding' and 0 to 1% CPU during this, no noticeable increase in memory.
I've shared a zip file with the contents of the fine-code-coverage folder under the tests - you should have a link in your email
Steps to recreate
Fresh build (clean + rebuild) - not required, but I've been doing this quite a bit in the hope it helps :)
Run unit tests, either all or a subset
switch to a code file to check coverage - OR -
click in the Fine Code Coverage window
Current behavior
VS becomes unresponsive, often with a transparent white overlay window and will not accept any commands
Sometimes, after killing devenv, and repeating steps above, it will work fine for a while (e.g. for some files) - very often when I use the FCC window to filter the behavior will immedately occur
Expected behavior
Coverage information should be shown
Here is a snapshot of the log (I cannot copy/paste it due to a hang)
Task manager
The text was updated successfully, but these errors were encountered:
Installed product versions
Description
Note: this only happens when the FCC extension is enabled. Only recourse is to kill the devenv.exe process. I usually give up waiting after some minutes. While I was gathering info for this bug report, I guess about 8-10 minutes passed and suddenly VS became response. Typically I have given up after 3-4 minutes :)
We have a monorepo with ~20 projects and 150k LoC.
DevEnv.exe is typically showing 'Not responding' and 0 to 1% CPU during this, no noticeable increase in memory.
I've shared a zip file with the contents of the fine-code-coverage folder under the tests - you should have a link in your email
Steps to recreate
Fresh build (clean + rebuild) - not required, but I've been doing this quite a bit in the hope it helps :)
Run unit tests, either all or a subset
switch to a code file to check coverage - OR -
click in the Fine Code Coverage window
Current behavior
VS becomes unresponsive, often with a transparent white overlay window and will not accept any commands
Sometimes, after killing devenv, and repeating steps above, it will work fine for a while (e.g. for some files) - very often when I use the FCC window to filter the behavior will immedately occur
Expected behavior
Coverage information should be shown
Here is a snapshot of the log (I cannot copy/paste it due to a hang)
Task manager
The text was updated successfully, but these errors were encountered: