Visual Studio 2013 crashing multiple times a day - visual-studio-2013

I have Visual Studio 2013 Ultimate with Update 4. Computer is Windows 7, 64 bit, 8gb ram, 1tb hd. Multiple times a day it will lock up and crash while I am doing normal coding operations. Sometimes its while i'm opening a file, or renaming a variable, or just typing code. It was doing this with Update 3 and Update 2. Does anyone know how to fix this?
edit 2: I started working in a secondary project for a different portion of program and noticed it only happens when working in my big project (22k lines, 70+ files). The new project im working in is only 10 files and 2k lines of code, and has not crashed for the week i've been in it so far.
edit: here is the xml error log when it crashes
<WERReportMetadata>
<OSVersionInformation>
<WindowsNTVersion>6.1</WindowsNTVersion>
<Build>7601 Service Pack 1</Build>
<Product>(0x1): Windows 7 Ultimate</Product>
<Edition>Ultimate</Edition>
<BuildString>7601.18526.amd64fre.win7sp1_gdr.140706-1506</BuildString>
<Revision>1130</Revision>
<Flavor>Multiprocessor Free</Flavor>
<Architecture>X64</Architecture>
<LCID>1033</LCID>
</OSVersionInformation>
<ProblemSignatures>
<EventType>CLR20r3</EventType>
<Parameter0>devenv.exe</Parameter0>
<Parameter1>12.0.31101.0</Parameter1>
<Parameter2>54548724</Parameter2>
<Parameter3>Microsoft.VisualStudio.Shell.ViewManager</Parameter3>
<Parameter4>12.0.31101.0</Parameter4>
<Parameter5>545487c9</Parameter5>
<Parameter6>501</Parameter6>
<Parameter7>2f</Parameter7>
<Parameter8>System.ArgumentOutOfRange</Parameter8>
</ProblemSignatures>
<DynamicSignatures>
<Parameter1>6.1.7601.2.1.0.256.1</Parameter1>
<Parameter2>1033</Parameter2>
<Parameter22>0a9e</Parameter22>
<Parameter23>0a9e372d3b4ad19135b953a78882e789</Parameter23>
<Parameter24>0a9e</Parameter24>
<Parameter25>0a9e372d3b4ad19135b953a78882e789</Parameter25>
</DynamicSignatures>
<SystemInformation>
<MID>2AAE6B99-B3F8-41BF-BE92-B48165152E42</MID>
<SystemManufacturer>MSI</SystemManufacturer>
<SystemProductName>MS-7721</SystemProductName>
<BIOSVersion>V30.3</BIOSVersion>
</SystemInformation>
</WERReportMetadata>

Related

Reduce log and other temporary file creation in Visual Studio 2019

My work development PC is resource-constrained with only 28GB for the main system disk. There is a 1TB external HDD and some data and applications have been moved there.
However, I'm still regularly running into Windows 10 "Low Disk Space" warnings which are triggered when free space drops below ~1GB. While actively working, this happens several times a week. You have to waste time deleting temporary files, emptying the recycle bin, etc.
There are naturally many causes, but the primary culprit in my case and the focus of this question is Visual Studio 2019. Whenever I perform even a simple build (C++ DLL and EXE projects), Visual Studio 2019 creates dozens of files all over the disk. After several days, the number can be in the thousands and GBs in size. Very few of these files appear to be essential - you can generally safely delete them while the project is still open in Visual Studio!
Examples include:
%LOCALAPPDATA%\Microsoft\VisualStudio\SettingsLogs*
%LOCALAPPDATA%\Temp_CL_*
%LOCALAPPDATA%\Temp\dd_BackgroundDownload*.log
%LOCALAPPDATA%\Temp\dd_updateconfiguration*.log
%LOCALAPPDATA%\Temp\servicehub\logs*
%LOCALAPPDATA%\Temp\VSFeedbackIntelliCodeLogs*
%LOCALAPPDATA%\Temp\VSRemoteControl*
.vs (eg. IntelliSense database)
and many more.
What steps can I take to:
reduce (or eliminate) all but essential temporary/cache files
move temporary/cache file generation to the external disk
request Visual Studio to clean up after itself when the IDE is closed
Don't bother with unhelpful comments like "get a larger disk". Even with a large local HDD it would be sensible to reduce the number and size of files hitting disk. Given enough time, any disk will eventually run into this problem.
I have been suffering the same problem for more than a year. There are many the occasions when I access my temp folder and I have seen hundreds and hundreds of directories and files with random alphanumeric naming pattern of 12 total length (########.###). And I did not know where it came from ...until I started investigating yesterday. Your question helped me to identify more temp files.
In the end you get used to it and stop giving it importance, but it is really uncomfortable and dirty since the number of files keeps growing and growing, and growing in size as well, and so on, until the next cleaning of the system.
For that reason I have developed a free extension for Visual Studio 2019.
You can download it from here:
https://marketplace.visualstudio.com/items?itemName=elektroHacker.VsAutomaticTempFileCleaner
And here is the repository for the source-code:
https://github.com/ElektroStudios/VsAutomaticTempFileCleaner
The extension will handle the Visual Studio's application exit to start deleting temp files. It only deletes temp files related to Visual Studio (so it does not empty the temp folder neither delete non-related files). Unfortunately some temp files are still in use / open by VS when closing the IDE, so they cannot be deleted (It could be done by delaying the deletion procedure executing a external process after VS process has been totally terminated, but it's too much work), but those files are a very little minority.
In any case, we can now say goodbye to the thousands of Visual Studio files that remain in the temporary folder pending for clean.
I hope this helps you and everyone concerned.

RAD studio takes very long time to open

I was using RAD 10.1 (Berlin) with no problem until now... Last month I applied Windows Creator Update and was occupied by other businesses... Now, each time I start the IDE, the loading progresses quickly up to "All design time packages loaded". At this time RAD studio sits on its splash window and consumes ~25% CPU. It takes at least 10 minutes before the IDE appears...
I've installed RAD 10.2 (Tokyo) and all provided patches, hoping for a fix... But the problem remains the same.
I can't go back to previous version of Windows 10 (more than 10 days after install).
I've already searched for an answer and Matthias E suggested that it was linked to https://quality.embarcadero.com/browse/RSP-17972.
But, in my case, the (very) long period stands only for IDE loading even when there is no project to (auto)load. I'm not talking about the time-period to load the project or to start project execution or even to start the application execution. Once the IDE has been loaded (after ~20'), everything (editing, compilation, building, debugging, execution) is working quickly...
I have become accustomed to never close the IDE once opened but this is particularly disturbing.
Could you help me ?
--- Edited ---
For those who cannot access the link above, here is the content :
Details
Type: Bug Bug
Status: Open Open
Priority: Major Major
Resolution: Unresolved
Affects Version/s: 10.2 Tokyo, 10.1 Berlin Update 2
Fix Version/s: None
Component/s: Debugger, IDE (Development Environment), Libraries/Frameworks
Labels: None
Platform: Windows 10
Language Version: English
Edition: Professional
InternalID: RS-83785
InternalStatus: Open
Description
The debugger goes haywire for everyone in our organization with Creators and Tokyo/Berlin. Reverting to Windows Anniversary brings back the sanity.
Debugger problems with Tokyo/Berlin and Creators:
App takes a long time to load with modules loading and unloading and re-loading many times
IDE freezes
Memory consumption of bds.exe explodes, sometimes (> 3GB)
I will attached before and after screenshots showing how modules load and unload and re-load with Windows 10 Creators.
I presume these problems have the same root cause(s) than those in https://forums.embarcadero.com/thread.jspa?messageID=884382*
--- ---
Thanks to Lieven Keersmaekers's suggestion to use procmon, I was able to find the cause of the problem. RAD studio was heavily trying to access an enormous (128 GB) zip backup file (see : qed-electronic.com/Download/170808-ProcMonTrace.jpg ). I've simply moved the backup file to another location and RAD studio now starts as before. I have no idea why RAD wanted so much to access this file : none of my project files were located in this zip. The Windows Creator Update was apparently not guilty...
bds.exe must be launch with only one CPU !
CPU Affinity CPU=0
Thx to Javorszky
https://community.embarcadero.com/forum/installation-issues/1408-running-from-ide-freezes-windows-10#4173
To run quickly without entring TaskManager and change Setting CPUAffinity,
just create a batch file on the desktop:
cd "C:\Program Files (x86)\Embarcadero\Studio\19.0\bin\"
start /affinity 1 bds.exe
Why ?
"The reason for this is that most applications you run these days have been designed with multi-core processors in mind and will work with the operating system to distribute their operations as evenly as possible across all the available cores. "
see : https://www.techrepublic.com/blog/windows-and-office/change-the-processor-affinity-setting-in-windows-7-to-gain-a-performance-edge/

Speeding up VS2010 when working with WF4 IDE

I am developing on our development server. Windows Server 2008 R2 64 bit OS, 256GB of RAM, 16 CPU machine. VS2010 with SP1 installed.
I have a huge workflow (around 30K lines in the XAMLX file). Every time I make even a small change in an activity, like changing the display name, it takes about 2-3 minutes to register the change. VS2010 is unresponsive all this time. It is extremely frustrating.
What is causing this and how can I make it run faster? Is there any setting in VS2010 that will make this run faster?
Thanks!
The most likely cause of the delay is the associated work flow designer trying to update to the change you just made. It's doing so synchronously on the UI thread and hence you see the delay.
The only way I can think of to stop this is to not open the designer. Instead just open the raw XML file and edit it directly. To do this
Close the file
Right click on the file in solution explorer and select "Open With"
Choose the XML editor
Also I encourage you to file a bug on connect about this behavior.
http://connect.microsoft.com/visualstudio

ReSharper slow and troublesome

Im using ReSharper 6 in a Vs 2010 Pro environment and are doing some pretty large scale projects. Development box includes 2 x quadcore xeon with 24 GB ram. Project's are running on a PCI-E x4 SSD drive with 1GB/s read and write (for real). So, i suppose there is not much I can do to give the development machine more power.
The worst project is an Umbraco site with roughly 14000 files and folders and some pretty nasty css. I got everything from second long freezes to 30 sec VS freezout.
I've optimized VS2010 according to every guide available in VS optimization. Even enabled the 64bit memory enhancement but the problems continue.
I've even added the media library folder to the skip list.
Are there any other magic tricks someone would know of, please let me know!
gorohoroh's comment lead me to the solution, the 6.1 nightly dec 13 rocks!
Thanks
http://confluence.jetbrains.net/display/ReSharper/ReSharper+6.1+Nightly+Builds
I am using 7.0.1 and I find that it's killing my machine too.
However, it normally happens if I have more than one VS2010 open.
If it happens then the only way of fixing it I have found is to close VS, delete the DotSettings.user and the suo, and then reopen.
I'm using 6.1, and find that it slows down over time, and typing becomes really laggy. I've just discovered that when it starts to chug, if I go to "Tools..Options..ReSharper..General", then click on Suspend, then Resume - it goes back to it's initial speed.

why is vs2010 so slow lately? Its nearly unusable

Not sure what has happened on my dev machine but I can barely use visual studio 2010 these days. I have a copy of professional edition installed on a win7 pro x64 build running on top of a i5 M430 and 6 gigs of ram.
With only VS2010 open i've seen the process leak away to 600,000k+.
The editor is extremely slow. Every character I type sends the gui into "Not Responding" for 5 seconds and starting/stopping the debugger is a ~30 second operation.
I've done a repair install. No change.
I've removed productivity power tools and installed the perfwatson extension.
When I installed perfwatson the GUI sped up a bit while opening/loading a project. But the text editor still has an awful delay.
What else can I do? Harware rendering is off in my environment options.
an example of the slowness (literally): typing Height="1024" takes about 30 seconds to display in the text editor and do its update flash to go out of not responding. The word "Height=" takes 5 seconds to show. The intellesense and blank " " takes another 5 seconds. Each digit pops in every five seconds after that.
Needless to say even trying to edit existing work is a frustrating experience.
edit: rolled back one version on video driver. No noticeable changes after reboot.
edit: did some winforms projects today. No slow issues with this project type. Must be something with just wpf/sl projects.
edit 8/18/11: Took troublesome project to the production server. VS2010 editor works great there. Very snappy and responsive. Not at all slow. So it's not something inside my project. It's something in my machine. But a full out OS rebuild is something I can't just do now. Probably will start a bounty soon.
Delete the .sdf and .sou that have the same base file name as your solution file.
If your solution file is
c:\MyProject\project.sln
You should delete
c:\MyProject\project.sdf
c:\MyProject\project.sou
This solves 98% of the problems of slow VS.
These files contain intermediate information that is not important for the functionality of the solution and as time goes by they swell up and become bloated and fragmented. VS relies on these files for and if dealing with them is slow, everything is slow.
I know this is an old post but I have just had an issue where my visual studio project has been working fine for about 2 1/2 years and suddenly every time I clicked run I had to wait about 3 minutes and the same when clicking stop. I tried the old windows reboot but to no avail.
I found a post about deleting the projects .suo file (it was only 4MB).
I deleted the .suo file and everything is completely back to normal. I guess the file had corrupted or something.
Having a large number of breakpoints or a large number of files open can cause serious performance problems, but it sounds like your problems are worse than that...
A bios update and a intel chipset update on my machine solved nearly all my performance issues.
The slowness started to creep out into the OS and I was pegging the cpu at idle. I've got 4 cores and 8gb ram. It shouldn't do that. Now its happy at 8% load at idle.
Thanks to those that tried to help.
had the same problem. not sure what causes this ridiculous performance nightmare, but eventually i had to re-install windows. This same issue was posted on Microsoft forums but the best answer was to re-install VS or windows.

Resources