VS2019 16.4.1 - how to cease all the 'background tasks'?

Question

_{Thursday, December 19, 2019 9:38 AM}

My VS always run something as a background process. How can I stop these unsolicited 'tasks in queue'? They take too much of time and make my VS unresponsive.

All replies (4)

_{Thursday, December 19, 2019 12:07 PM}

What tasks are running in background?

_{Thursday, December 19, 2019 1:50 PM}

That's another question , and I don't know how to identify or view the list of those tasks, do you?

_{Friday, December 20, 2019 6:30 AM}

Hi Senglory,

Welcome to MSDN forum.

According to your description, you could refer to below steps to troubleshoot this issue.

#1. You could try to open Visual Studio in Safe Mode by opening “Developer Command Prompt for VS 2019” -> enter devenv /safemode to start VS 2019 and avoid the impact from other third-party extensions and plugins.

#2. Please try to repair/update VS 2019 to the latest version by opening Visual Studio Installer -> find VS 2019 -> More/update -> Repair.

According to this thread Visual Studio 2019 un-terminating background processes – high cpu use, lag, if possible, you could try to add a rulset with the following contents as a workaround.

<?xml version="1.0" encoding="utf-8"?>
<RuleSet Name="MyRules" Description="My Rules" ToolsVersion="16.0">
  <Rules AnalyzerId="Microsoft.CodeAnalysis.Features" RuleNamespace="Microsoft.CodeAnalysis.Features">
    <Rule Id="IDE0067" Action="None" />
    <Rule Id="IDE0068" Action="None" />
    <Rule Id="IDE0069" Action="None" />
  </Rules>
</RuleSet>

And refer more detailed information from this link: Specify a rule set for a project.

BTW, I notice that this might be a potential issue, and you could report this issue to the VS product team directly, from Help -> Send Feedback -> Report a Problem…

Below are some similar issues and you could also refer to them:

DisposableFieldsShouldBeDisposedDiagnosticAnalyzer eats up memory resulting in VS crash

Running low priority background processes never completes

I hope all above could help you.

Best Regards,

Tianyu

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].

_{Wednesday, December 25, 2019 10:51 AM}

Hi Senglory,

There is one possibility that this be caused by some third-party extensions, temp files or any other tools integrated into VS.

So when you start your VS, VS will run these extensions or loading some relevant documents.

Or please delete all the temp files in the path: C:\Users\xxx\AppData\Local\Temp

Besides, use devenv/safemode to use your VS. It will prevent loading any third party packages and give you a clean environment.

Best Regards,

Perry

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]