Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Visual Studio frequently hangs after running unit tests #470

Open
biggik opened this issue Dec 4, 2024 · 1 comment
Open

Visual Studio frequently hangs after running unit tests #470

biggik opened this issue Dec 4, 2024 · 1 comment

Comments

@biggik
Copy link

biggik commented Dec 4, 2024

Installed product versions

  • 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)
image

Task manager
image

@tonyhallett
Copy link
Collaborator

With a large project two types of FCC options can cause an issue.

NamespacedClasses is one - set to false.

HideFullyCovered, Hide0Coverage and Hide0Coverable - set to false.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants