I've just installed the Visual Studio 2012 RTM on a Windows 7 x64 desktop.
Unfortunately, I'm very underwelmed by the performance of the out-of-the-box installation. Everytime I try to rename a file in the solution explorer, change to a MVC cshtml editor, open a designer view, or intellisense pops up when I start typing with the c# editor, the whole visual studio applications hangs for 5-10 seconds.
There are no customizations, plugins, extensions enabled here that do not get applied with the standard installation.
Has anyone else experienced this? Has anyone else found a way to log the application faults which occur, or detect the hang. I need some way to determine what is going wrong, in order to identify what needs to be altered to rectify the installation.
The problem is you are consuming the lot more resources of the system which is causing hung state of VS. Please close any of other application who is using more RAM. You can take the help of Task Manager to close those application. Please keep in mind if you are running SQL standalone database instance services then its also causes the hand issue. The best is keep you system free from running unuseful application or Go for System upgrade. :-)
Related
For over a month now I've been experiencing problems with VS2017 on my home PC. I even tried submitting the feedback to Microsoft. There's more info about the problems I'm experiencing there.
The problem:
The gist of it is that VS is eating RAM like crazy. As soon as I start opening files, adding new files, using IntelliSense, building or (especially) debugging, the RAM usage skyrockets.
After that it's only a matter of time before the VS crashes and restarts without any error message. Though there are numerous error messages throughout these breif ~20min I have with each session.
Additional details I observed:
Doesn't happen with Python projects, as these don't have to be built constantly. It might be eventually happening if you debug a lot, but I didn't have the chance to check that because most of my Python coding is debugged on an external device
Size of the loaded solution doesn't matter;
UWP and WPF seem to crash the most. Console Projects take longer to crash.
Also affects .NET Core;
It doesn't matter which version of .NET Framework I use;
VS2015 worked perfectly, but I don't have it anymore after the format
What I already tried:
I reinstalled VS;
I refreshed Windows;
I reinstalled Windows;
I checked my drives and RAM for issues - none found;
I switched from Community to Enterprise;
I tried disabling extensions;
I applied some shady hotfix I found somewhere;
Finally, I installed Rider which seems to be the best solution as of now. It still lacks many important features, though.
Is there anything else I can do/try/check? Did anyone experience (and fix) a similar issue?
Cheers!
You get a System.OutOfMemoryException, this means your Visual Studio runs out of free virtual address space (4GB on 64 Bit Windows for the 32Bit Visual Studio because Visual Studio is configured to be large address aware and MS refuses to release VS as 64Bit program which would fix this issue).
To analyze the memory usage, you need to run WPRUI.exe (part of Windows Performance Toolkit (which gets installed by VS2017) for some scenarios, if not, install it on your own), select Reference Set (Note: expand the Resource Analysis entry first to see all options).
and click on Start. Capture the memory usage grow for some 100s of MB and click on Save.
Open the generated ETL with the analyzer (WPA.exe) and analyze what the process devenv.exe is doing.
Also zip the ETL + NGENPDB folder (important) as zip and attach it to your bug report so that Microsoft can analyze it.
I have successfully used the WPRUI and WPA applications in the past, the last time a month ago, to identify performance problems in our C++ applications. But today I recorded a new trace of one of them, and open it just to see WPA crashing.
It's reproducible every time by opening an ETL and going to Graph Explorer -> Computation -> CPU Usage (sampled) -> unfold. Just clicking to see the CPU sampled graph list. Sometimes it crashes silently, sometimes with the dialog that lets you debug the crash.
Has anybody experienced problems like this? I don't see any support forum in the Windows Performance Toolkit site, and I would like of course to find a solution for this. Any hints are greatly appreciated, thanks in advance.
PS: reinstalling doesn't help. Neither does removing user preferences. The stack only showed me a problem accessing memory out of bounds, in a "Task" class, but I can't get the debug dialog to show again (it's crashing silently now, every time).
PS2: the only significant change I remember to have done in this past month is installing the CTP of Visual Studio 2015, and letting Windows upgrade a bunch of packages it had pending (I'm in a capped subnetwork and Windows doesn't upgrade automatically).
The VS2015 CTP installs a .Net 4.6 pre-release version. Maybe this .net versions causes the issue. So remove VS2015 CTP and the .Net 4.6 Preview and reinstall .Net 4.5.2.
Everything had beed working great, but suddenly something happened and every time I try to open any web-based project (either MVC or just 'Open Web Site', any others are just fine), Visual Studio 2012 crashes with Windows environment message:
MyProject - Microsoft Visual Studio (Administrator): devenv.exe - System error
Exception Processing Message 0xc0000005 Parameters 0x000007FEFD4A718C 0x000007FEFD4A718C 0x000007FEFD4A718C 0x000007FEFD4A718C
ОК
I did not notice exact moment when it stopped working. And obviously I have different extensions etc. But I believe, I did not install any big soft these days.
I've installed Windows 8 though, but separatly - on separate volume to try it. Theoretically, it might affect my situation, but I don't know how is that possible - at least I don't know any explanations.
I've tried to refresh Visual Studio 2012 installation, even removed and installed it again.
However, at the same time, I have Visual Studio 2010 previously installed, and it opens web-based projects without any problems.
Mentioned error message above is, as I understand, some generic error message - googling did not help on its recognizing, so don't know what to do - don't really want to reinstall Windows because of that.
Does anyone have any thoughts? Thanks!
I really don't know what was the cause of the problem, but after all other tries I've applied all pending updates of Windows Update service and everything works well after that.
When I am trying do deploy/debug etc. my hosted app :
I am writing good credenials, and then something strange happen what happen only on one machine (sad to say it's only mine).
After putting sign in button (keep me signed checked/uncheced 100 times) it's would not login, but open sharepoint 2013 site in this window:
What I did:
reinstall visual studio
update visual studio
restart computers
clear cookies/catche etc.
Solved accidentally by installing CKSdev tools but only for one run...
It once happened to me that while it was a debug version all credentials were always rejected. I still don't really know why (it was a big project, not fully made by myself), but as a temporary solution you may try hardcoding your credentials. It's not perfect, but it may be working ;)
The one and only solution was reinstaling the windows, i didn find any other solution
edit:
After the newest updates this problem is solved
I followed the instructions in this link: http://msdn.microsoft.com/en-us/library/bt727f1t.aspx to install the remote debugger (2012) on my server where the application is running in hope to debug it remotely from my dev machine running visual studio 2012.
I cannot even get as far as viewing the list of processes to attach to on the remote machine. I keep getting "Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named [name]. Invalid access to memory location".
I have managed to successfully connect a few times but then the attach fails immediately then I cannot connect again.
This is causing huge issues for me as I cannot remote debug anything. I must be missing something glaring. Please someone give me a solution.
I've found the only way to correct this is by restarting Visual Studio.
Worked for me. I found it at this blog post about invalid access and remote debugging.
It turns out the one thing I missed was to tell Visual Studio where to find the .pdb symbols relating to the remote process. To do this go to Tools -> Options -> Debugging then in the Symbol (.pdb) locations add the remote location to the pdb files.
To clarify, I was attaching fine but could not break into code. Now I can. Be aware though that there are other hurdles before you get to my stage where I was attaching to the process successfully but could not catch a breakpoint.
I recently had someone else report this and debugged the issue on their machine. The "Invalid access to memory location" errors are due to an issue in Windows, it can be addressed with this hotfix.
I have had this problem in VS 2012, 2013, 2015 and 2017. Based on other answers it is likely that the problem is related to running a 32 bit version of Visual Studio on a 64 bit PC. Sometimes, as others have recommended, restarting Visual Studio fixes the problem but the best solution I've found so far is to start Visual Studio without a solution, open Debug -> Attach to Process, change the Connection Target to the remove server and wait for the process list to load. Then Cancel, do not attach yet. Load your desired solution and then come back to Attach to Process and the remote process list will still be loaded. Connect to your desired process and everything should work properly from then on.