Visual Studio 2019 Community Edition 16.7.0 hanging - visual-studio

I have an issue with Visual Studio 2019 Community Edition 16.7.0 (at the time of writing the latest version).
If I create an empty project I have no problems at all, however if there is even one C# file then Visual Studio becomes absolutely useless. I've observed the following:
CPU usage hovers around the 40% mark.
Loading a file takes over 5 seconds.
Intellisense fails to recognise anything.
Every minute or so the entire application will hang for a few seconds.
After a few minutes it hangs and does not recover.
This did not occur before I upgraded to 16.7.0, but as for what I was on before I'm not certain. I've tried a number of routes:
Removing the .vs folder.
Removing the project and solution and re-creating them.
Running Visual Studio in SafeMode (this simply brought up a large number of exceptions when trying to load a project).
Running the ResetSettings switch.
A fresh installation of Windows 10 x64.
Disabling the Load projects faster option.
All extensions are disabled.
Here is what the 'status' area looks like initially during project load and then while hanging:
How can I fix this?
Failing that, how can I roll back to an earlier release?

Related

Visual Studio slowness, possible reason?

Im struggling with extremely slow Visual Studio. I use it to build C++ projects mostly.
Everything could be super slow. Menu's loading, intelIsense tips, builds. I've just tested building simple solution in 1 file, and build took around 5 minutes. But! I found this article about Windows Performance Analyzer which I used to trace this solution build. Despite overall time taking around 5 minutes, WPA report build took only around 0.686 seconds, attaching screenshot:
apparently I press "rebuild" in VS and build itself started ~300 seconds later(timeline).
Currently I use VS2019. Same problem I observed on VS2017. I did removed all VS components and installed VS2019 and problem is not gone. All other programs run fine. No excessive CPU load(intell 6700k), no noticeable harddrive usage(windows and VS components are on m2 ssd, lightning fast), 32 gb ram and enough free space on system disk.
Only VS extension I installed myself is QT extension for VS2019. Which actions can I take next to find the problem?
Things to try:
devenv /safemode from a command line starts the IDE in safe-mode with all plugins disabled.
Visual Studio Installer and repair install
Disable graphics acceleration in Visual Studio (Tools|Options|General ... there are a few "rich client visual experience" related things)
Check paths on your computer. If other apps run fine but one does not, it could be that this app tries to access a network drive or website which is not available.
Run "procmon" and "procexp" (Process Monitor/Process Explorer from Sysinternals) and take a look at what's going on.
Try VS 2022.

After upgrading to Visual Studio 2019 16.7.1 the program hangs

I use Visual Studio Community 2019 with C++ (no .Net). Yesterday I updated to version 16.7.1. Ever since then, Visual Studio hangs on exit at the step "Unloading Projects". No projects are unloaded, and the progress bar never starts moving. The program simply hangs and is unresponsive. The only way out is to kill the process.
It also hangs whenever I try to change the Configuration target for the solution. Both issues occur on any of my solutions that I open. I have tried using Visual Studio Installer to repair the install, but it makes no difference. The installer does report one issue: Couldn't repair Microsoft.AspNetCore.TargetingPack.3.1.3.1.3 But this hardly seems like it matters to my Win32 projects.
This problem definitely started as soon as I updated to 16.7.1. I don't recall the previous version I had, but I had just updated a few days before so it was probably 16.7. I am posting to see if others have this problem and if anyone has found a solution (other than falling back a version). I will limp along with it for now.
Same happened to me. Just use visual studio 2017. Only thing that fixed it for me.

why is my Visual Studio 2019 Pro so slow debugging, after doing Visual Installer update?

VS2019 was working fine.
Then I ran Visual Installer and added "Mobile development with .NET".
After than, visual Installer "update" button was showing, so I did the update.
But now when I stop my VS2019 project at a breakpoint, single stepping is very slow, taking many seconds per step.
Tried restarting VS2019, and restarting my Windows 10 Pro, but got same slowness.
Opened same project with VS2017, it is debugging is OK, no slowness.
The resolution I found was that the culprit is not Internet, RAM, or CPU.
It is the Disk Usage. Check for your disk usage under the Performance tab in Task Manager. Try and find out which process (Anti-Malware/ anti-virus/ant other process) is eating up your resources.
Kill the culprit and it works smooth. For me, it was Disk Scan Service and Windows Search Service (which is fairly useless).
Check this link to kill the Windows search service.
Comprehensive deletion of all contents of %TEMP% worked for me -
https://developercommunity.visualstudio.com/content/problem/516141/very-hight-cpu-usage-by-visual-studio-2019.html
I can't believe is 2020 and MS can't stop spaffing crap into a temp directory which causes their software to slow to a snails pace with some kind of infinite processing issue. Jeez.
For me it was NVidia NSight for visual studio. Uninstalling it from the windows application list was the only option as it wasn't showing up in the VS2019 Extensions manager.
For me it turned out to be a problem with the installation. I had old versions of Visual Studio and .NET libraries still on my machine. I did a full uninstall of Visual Studio, .NET Core SDK, .NET Framework, etc. and then re-installed Visual Studio 2019 and just the .NET libraries that I needed. After that VS 2019 debugging is speedy.
I was experiencing the same issue stepping over one line of code took me 1400 ms on my VM and 6 ms on my coworker's VM. (Earlier this week he had copied my VM so essentially we were on the same machine).
Took me some time but then I remembered a change I did to my visual studio.
Earlier that week I needed to step into one of our DLLs. To do this I changed my debug settings under Project Properties --> Debug --> Debugger engines. I Checked "Enable native code debugging". This was wonderful to allow me to debug into our DLL and see what was happening on the other side, although it dramatically slowed down my debugging (233x slower to be exact!!!!).
The performance change will different per your solution and how much you are inheriting, but unchecking this did the fix for me!
Delete .vs folder where locate in your project root directory after backup.

Visual Studio 2013/2015 Idle CPU usage

I'm currently evaluating Visual Studio 2015 RC. I've noticed when running the IDE, The Visual Studio 2015 process is constantly at around 25% CPU usage. Even without a project loaded and without the welcome page it is gobbling up 25% CPU usage at a constant rate. No other applications running other than background services. All other running processes use around an additional 2 to 4 percent CPU overall.
This behavior has also been noticed in Visual Studio 2013.
Is anyone else seeing this behavior? Is this normal? Any suggestions?
Had this same problem. Processor constantly at 45-50% even when the IDE is completely idle.
Turns out the problem is the Microsoft Git Source Code provider.
I turned that off and processor dropped to 0 and the IDE became much more usable.
In my case disabling Telerik ASP.NET MVC Extension solved high CPU issue.
High CPU load started on solution load and didn't drop (40% with one, 80% with two solutions) until VS was closed or even sometimes after (had to kill the process).
Tools->Extensions and Updates->Installed, find the extension and click 'Disable'.
In my case all reference counts tried to update every time when I edit code.
I have just turned them off. You can do it this way.
It’s not to be expected that Visual Studio should chew up continuous CPU time.
I am running Visual Studio 2015 Community RTM right now with a medium sized project open, and am not seeing any ongoing CPU usage (according to Process Hacker 2, which shows usage as small as 0.01 percent). It’s just blank, which means not even 0.01% CPU usage is registering.
Keep in mind that IntelliSense scans your project files in the background to build the database for popping up its suggestions, etc.
Choosing Project > Rescan Solution from the menus will result in that process being done over, which will cause the CPU to be used for a time. But it should ultimately go quiet.
Seemingly forever, there have been times when deleting the Intellisense Database files and doing a full rescan solves “odd behavior” type problems. I don’t know if it’s the “prescribed” method, but if I suspect an IntelliSense problem I just delete the .sdf file in the project folder if I want to make sure Visual Studio starts with a clean slate. This isn’t necessary very often.
I also had this problem, constant 20-40% CPU when idling (Visual Studio 2015 update 1). I noticed that other local repositories of the same code did not have this problem.
I deleted the problematic local repository and took a new checkout, this solved the issue for me. Why this worked, I unfortunately cannot explain...
I run resharper, turned that off and turned off the Microsoft Git provider and still had high CPU issues, devenv.exe would also run after close... until recently.
It appears VS 2015 Update 2 has resolved these issues!
https://www.visualstudio.com/en-us/news/vs2015-update2-vs.aspx
In my case; "Visual Studio 2015 Update 1" gone crazy editing JS files regarless of the length of the source. It used high CPU and the editor is even freezed. I fixed the issue by disabling the 3rd party add-ons by one-by-to detect the buggy one causing VS 2015 malfunctioning.
Hope it works.
In my case, the culprit was Node.js tools for Visual Studio. I had v1.1.2 installed and the cpu was constantly around 25-40%.
A switch to Node.js Tools v1.2 RC resolved the problem completely after an initial high load that went away in a couple of minutes.
In my case it was either the Roaming Extention Manager or most probably the azure worker role project in my solution. If you have one of these try unloading it and restart visual studio. I can reproduce it but I don't know why it happens.
I've noticed also that when running and stopping a debug episode on the local server, if the page is still open in the browser, VS will continue to run at high CPU. Closing the browser page stops this.
I want to share my experience,
In my case I had to diable all extensions and updates and code analysis c#.
1-For extensions and updates :
Tools => Extensions and updates
2-For the code analysis
Solution explorer => right click on the project => Properties =>Click on the tab "Code analysis" => click on the "Open" bouton => Uncheck the checkbox "Microsoft.CodeAnalysis.CSharp" => save and exit.
Cpu usage descended to 1 %.
In my case, The .suo file in Visual Studio was the culprit. Deleting it fixed my issue.
Refer below link for more details.
https://shemeerns.com/2014/04/04/the-solution-user-options-suo-file-in-visual-studio/

Visual Studio 2013 - Slow Extension or Add In - how to find which one?

I have a solution with about 40 projects in it. When I load or unload a project it takes up to 5 minutes and hangs the development environment for the entire time. When I go into safe mode it is about 5s or less. I don't know proc mon very well, but it did show lots of file access outside the project in question.
I'm assuming this is caused by an extension or add in. How do I figure out which one. I have disabled all the ones I can disable but a large proportion of my extensions cannot be disabled. Do I really have to uninstall them all in turn?
Cheers,
James
You can use Process Explorer to find what module in Visual Studio is currently running when VS hangs from the DevEnv.exe process Properties - Threads tab.
DevExpress Assembly Deployment Tool v1.1 with DevExpress 13.2.7
I have discovered why my Visual Studio Environment has been so slow (unusably slow – 10 minutes to do 5 second tasks – locked application for 10 minutes at a time).
Solution is to uninstall VS extension DevExpress Assembly Deployment Tool v1.1.
As detailed here:
https://www.devexpress.com/Support/Center/Question/Details/Q570295

Resources