I'm running a Python 2.7 server in Visual Studio 2013 (update 5) with PT4VS, Twisted, and P4V integration (I mention these details because they may be related to the lockup). Periodically Visual Studio freezes (but never goes white like most processes do) and becomes unusable for a minute or so. This is happening several times a day not just for myself but for our entire development team and, of course, it's really annoying.
I tried Googling for a solution but came up dry. What I'd like to know is, is there a way I can see what Visual Studio is doing during this locked time so I can maybe pin down what the issue exactly is.
Related
I've been working with Visual Studio 2022 for a couple of months now, and I've used previous versions for years without any problems.
Today I copied a piece of code to rearrange it, saved right after and the program froze so bad I had to restart my whole system.
Ever since this happened I cant use the software, any time I try to do so it completely freezes my system after a couple of minutes, no matter which of my solutions I open or if I create a new one. I've also noticed it being much slower than it used to be.
I also don't use any extensions besides a color pack.
I use VS Code on the side as well, I don't experience any problems with it, I also doubt that my system is out of memory as I usually have 20+gbs of ram available.
Should I just reinstall Visual Studio completely? I really cant wrap my head around some corrupted files causing so much trouble.
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.
The problem
When using Visual Studio 2013, Ultimate update 5, the IDE becomes very laggy (not running anything), and CPU spikes eating consistently around 30% up to 100% CPU.
Particulars (what I am doing when this happens)
This happens quite often and doesn't seem to be dependant upon any specific project. I have tried re-installing (fresh), as well as from scratch (format, reinstall windows, install ONLY visual studio + a very moderate suite of developer controls [2 well known companies (DevExpress, and Telerik)])
What is also very odd, is this happens even when developing a console application, although it takes much longer for this to occur.
The system I am running is more than adequate (according to their specs required), and Visual Studio is really the only application experiencing this lag + cpu spike issue.
(notice the cpu spike to 58%. this was also visual studio doing that in the background)
This is not a code issue, but an issue somehow with the IDE itself. What I am hoping for is a solution involving something that I may need to tweak / adjust / disable / etc which is contributing to this. As an aside, I really have no idea why there are so many handles open when Visual Studio is running. 91k seems quite excessive.
Another issue (pointing it out as it may be related), when publishing a project, after publishing, Visual Studio keeps automatically checking 'Click Once' when I have explicitly disabled it. This needs to be unchecked after every time I publish or else the next publish/compile/test run, results in an 'mscorelib' message complaining that the pdb doesn't exist, even though it does, and I have used it in other projects. What is frustrating about this problem is that I am telling it I don't want the project to be clickonce, and after it builds a non-click once project for publish, Visual Studio enables it effectively making this checkbox useless and wasting valuble time having to do this after each publish. Time, that adds up -- especially with the persistent lag.
I am confident I am not the only one who has experienced this due to reproducing this issue on a fresh and bare setup of both the operating system, and visual studio with nothing else aside from two popular component suites. As such, this is my attempt to reach anyone else who has experienced this, and if you did find a solution (or cause), to lend a hand to me.
While updating or uninstalling Visual Studio Installer Projects Extension Preview the step "Microsoft Visual Studio Preparation" is taking enormous amount of time. I may say it gets stuck.
My suspicion is the installer (Windows one, not the extension itself, since it is getting modified--updated or uninstalled) is making changes to the registry.
VS registry entries are too many to investigate them one by one. Re-installing VS is not an option. (I have VS 2013 Ultimate on Windows 8.1.)
So, my question is: is there any tool to repair, optimize, clean, or otherwise modify registry (VS portions only) to get the process quicker? Or some sensitive keys that need to be explored? Seems like there are timeouts involved? (Although I do not find this quite reasonable...)
Or, if I am wrong about the registry, Is there another reason for this symptomatic behaviour? UAC issues? NTFS security? Other?
Any advice?
Thanks.
I just solved a similar issue with installing Visual Studio 2013 Update 3. It was taking over an hour on the "Microsoft Visual Studio Preparation" step.
I fired up Process Monitor from Sysinternals and realised the installer was busy logging to C:\FusionLog. Killed the update process, changed the relevant settings under HKLM\Software\Microsoft\Fusion to turn off assembly bind logging, rebooted to make sure the new settings were recognised, and voila, the "Microsoft Visual Studio Preparation" step took on the order of 10's of seconds.
I hope this helps with your problem because this was extremely frustrating for me. I wasted most of my work day on this.
When "Microsoft Visual Studio Preparation" is shown, the installer is running "devenv /setup" to register any packages and templates. That can take a long time. Though it's not ideal, it's not a bug; it's how Visual Studio works.
See this blog posting: http://blogs.msdn.com/b/heaths/archive/2014/01/21/upgrading-visual-studio-2013-update-to-a-newer-update-may-be-slow.aspx
It basically says there's no workaround to save time, just sit tight:
"There is no current workaround that will save time. You might consider starting the upgrade before taking a lunch or heading out for the day."
It also says the issue has been resolved for future versions of VSUpdate and Visual Studio.
Try to block the antivir activity. As for me, it significantly raised the speed.
I'm experiencing some performance problems. When I edit a file, Visual Studio 2008 performs a background (on-the-fly) compilation and then, it updates the error list. During this time, the cursor in the file editor disappears, and the keys I press to move or type more character are buffered.
Once the background compilation is finished, the changes are reflected in the editor (1 - 2 seconds). Every time I edit a file, which happens often, this happens.
How can I fix this problem? If this is not possible, can I disable this automatic build?
I had an odd performance-related issue today. My Microsoft Visual Studio seemed to be taking far too long to perform even the simplest of operations. I Googled around and tried a few ideas that people had such as disabling add-ins or clearing Visual Studio’s recent projects list but those suggestions didn’t seem to solve the problem. I remembered that the Windows SysInternals website had a tool called Process Monitor that would sniff registry and file accesses by any running program.
It seemed to me that Visual Studio was up to something and Process Monitor should help me figure out what it was. I downloaded the most recent version, and after fiddling around a bit with its display filters, ran it and to my horror, I saw that Visual Studio was so slow because it was accessing the more than 10,000 folders in C:\Users\krintoul\AppData\Local\Microsoft\WebSiteCache on most IDE operations. I’m not sure why there were that many folders and moreover, wasn’t sure what Visual Studio was doing with them, but after I zipped those folders up and moved them somewhere else, Visual Studio’s performance improved tremendously.
The Windows SysInternals website has a number of other useful utilities for network management, security, system information and more. Check it out. I’m sure you’ll find something of value.