currently using Visual Studio 2015. And at random occasions when I am debugging my code Visual Studio 2015 will get "Not responding" and never start again so I have to restart the application. First I thought it was due my code, but it's not (I think) It doesn't always crash but it does crash 8/10.
And always at random locations sometimes just when I start debugging, and sometimes when I debugged half of the code and sometimes just at the end.
And I am the only one that is facing this issue?
Must have been something with my computer.
I did a fresh install and so far I have not had any issues while debugging.
It seems like you might need more memory for VS 2015. VS2015 takes more memory comparing to old versions.
Related
I have Visual Studio 2015 version 14.0.25420.01 update 3.
When i start my program from the environment with local debugger and after that try to make a change in the code, most of the times visual studio crashes, and in some i don't see the changes and the keyboard is not responding anymore.
If Visual-studio doesn't crash, i can fix the non-responding keyboard issue by closing and opening the project again, it allows me to continue my work. This problem happen on every project that i am trying to work on, so code doesn't really matter here. I also have earlier versions of Visual Studio and they work fine without this issue. Any ideas?
To be clear: Visual Studio crashes only when i edit my code while running it.
I have installed Visual Studio 2015 Community Edition via Unity's installer and some of the options windows look like this:
Nothing fixes it; uninstalling-installing, formatting or installing on different machines. Apparently no one complains about this issue because there seems to be nothing on search results, but I'm 100% sure that everyone is experiencing this issue. When you open Visual Studio on its own, problem goes away, it works like it should. However, making Unity open Visual Studio causes it. I assume that this is caused by Unity forcing Visual Studio to load a plugin (probably Visual Studio Tools for Unity) which is actually incompatible with almost everything in Visual Studio.
Is there a solution to this problem? It drives me crazy and I don't want to use MonoDevelop.
I have the problem that Visual Studio 2013 crashes when I lock the computer or start another instance of Visual Studio.
I use Visual Studio 2013 with latest patches applied. I always start Visual Studio as Admin.
This seems to only happen with a certain big solution. This problem did not occur to me with other solutions.
I tried to delete the solution and make a clean checkout from TFS, but Visual Studio still crashes.
I know this is not much information, but do you have any idea how to fix this or how to what else I could check?
Additional Information: This still happens even with Visual Studio 2015 on a fresh Windows 8.1 installation...
Here's the error:
Use the following steps to solve the issue:
Source: http://resharper-support.jetbrains.com/entries/24765142-Visual-Studio-with-ReSharper-is-freezing-and-or-crashing
I would copy the solution with quotation but as you can see, there is a lot of text to edit.
Start Visual Studio using the /log switch. Then check the created log file for warnings and errors:
%APPDATA%\Microsoft\VisualStudio\11.0\ActivityLog.xml
If you use a Web Browser to view the file, it will be nicely formatted, due to the accompanying xsl-sheet.
I am running VS 2013 ultimate on win 8.1 Parallels and everything was working fine, now does not. I have repaired the install, and have even uninstalled and reinstalled VS 2013. WHen I run devenv.exe the initial VS loading screen shows and just spins. When I look at Task Manager, I only see VS running as a background process and eating up the CPU.
When I select a solution file or xml file as an example and choose the VS 2013, VS comes up and loads the file. Any ideas of how to get this working would be GREATLY appreciated.
I was able to get the IDE to come up in safemode, so I figured it was one of the third party addins. It seems like the Productivity Power Tools addin was the culprit in my situation.
Mostly it happens if we open a team project from tfs 2008 or tfs 2010, but crashes can happen any time.
When VS is closing down, it crashes nearly every time.
Tried trial RTM and our MSDN download - same story. Tried on three different PCs - same issue. Tried on 32 and 64-bit Windows 7 and Windows Server 2008 R2 - crashes.
Is it just our luck or does it happen to you to?
Here are some tips that will hopefully help you identify the problem:
http://blogs.msdn.com/kirillosenkov/archive/2010/02/08/how-to-investigate-and-report-visual-studio-issues.aspx
Ideally, get a call stack of the devenv.exe main thread with symbols loaded, and post it here (or even better), attach to the Connect bug. From the stack we'll likely be able to tell what kind of problem it is.
I logged it as an issue on Microsoft Connect.
There is a new release of the TFS Power Tools and Visual Studio 2010 Productivity Power Tools which seem to reduce the instances of VS crashing (although it still seems to crash from time to time). It might be worth checking out if you use either add-in.
Apparently, the crash was caused by using a DNS name in Connect to Team Foundation Server.
I replaced that with the IP address of the TFS server and the crashes went away.
We have two Windows Server 2003 DNS servers, and it looks like Visual Studio 2010 does not communicate with them correctly. Visual Studio 2008 connects to the TFS without any issues.
Apparently, there a bug:
"Large Visual Basic project crashes when closed"
http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=29797