Visual Studio 2012 Memory Spike and Hanging - visual-studio-2012

Recently, Visual Studio 2012 has been acting up. As I'm developing ASP .NET applications I routinely tab between the browser (Chrome) and the Visual Studio IDE. Sometimes when I attempt to tab back into Visual Studio the window will not come up. At that time if I look at my task manager I'll see that the devenv.exe process is using about 10 to 20% of CPU time and is gathering more and more memory for itself. This goes on for about 20 seconds or so before the IDE is responsive and usable again. Eventually, the IDE can't recover and I need to terminate the process.
My desktop is a 64-bit quad-core i7 # 3.4GHz with 8 GB of RAM, running Windows 7 OS. Typically devenv.exe will use about 500 MB of RAM. When the problem above begins to happen it will quicky ramp up to 1.5 GB and has been as high as 2 GB.
The only add-on I'm using is ReSharper 7.1. I have no further IDE customizations apart from the built-in dark color scheme.
EDIT — I have tried disabling and removing R# which has had no effect on this problem.
EDIT — Bug report on Microsoft Connect

I used to have this all the time until I installed VS 2012 update 4 then it all went away.
I also only use resharper ( version 8).

Related

Android Studio Bumblebee crashes frequently

I am wondering if anyone else has encountered this problem and figured a way to deal with it.
Android Studio Bumblebee crashes randomly and frequently. There is no pattern. It crashes when I do something (e.g., editing code) or sometimes when I do nothing. It can crash soon after I start AS or after I use it for a little while. It crashes once every hour or so on average.
Are there any parameters that I can change to make AS stabler? Is there a good way to diagnose the crash?
I usually have over a dozen programs running on the same computer (Visual Studio, Outlook, browsers...). AS is the only program that crashes. All others work fine.
Android Studio Bumblebee | 2021.1.1
Build #AI-211.7628.21.2111.8092744, built on January 19, 2022
Runtime version: 11.0.11+9-b60-7590822 amd64
VM: OpenJDK 64-Bit Server VM by Oracle Corporation
Windows 10 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 4096M
Cores: 16
Registry: external.system.auto.import.disabled=true, debugger.watches.in.variables=false
Non-Bundled Plugins: com.intellij.marketplace (211.7628.36), com.thoughtworks.gauge (211.6693.111), org.jetbrains.kotlin (211-1.6.10-release-923-AS7442.40), com.android.aas (3.5.1), com.google.mad-scorecard (1.2), org.intellij.plugins.markdown (211.7142.37)
I faced the same issue until I disabled the Launch in tool window. Just go to File -> Settings -> Tools -> Emulator and disable the launch in a tool window checkbox.

What can i do with Android Studio Virtual Device slow when running and freezing computer when closing?

When I run the Android Studio AVD that comes with the IDE, the device is a bit slow and when closing the device (with the close icon) the mouse stops moving and the screen starts to flicker (by blinking I mean the Android Studio IDE disappearing at random intervals), then stops like after two minutes and then the virtual device shuts down.
I have proved with three devices at API 25:
Nexus 5 -Nexus 5x -Nexus 4
With Nexus 4 the app is faster, but is the same problem when closing it, it freezes my PC.
I do not the causes and makes working with android studio slow and annoying.
Today when closing the emulator, it freezes like two minutes and Windows 10 gave me a blue screen with the error: Driver Power State Failure.
Any solutions?
My computer specs:
Windows 10
Intel core 7
8 ram Gb
64 bits
If your android studio gets hang multiple times then you can try this below step :
-> Go to help in Android Studio -> click on Edit custom VM Options then Paste Below Text :-
-server
-Xms2G
-Xmx4G
-XX:MaxPermSize=2G
-XX:ReservedCodeCacheSize=1G
-XX:+UseConcMarkSweepGC
-XX:SoftRefLRUPolicyMSPerMB=100
-Djna.debug_load=true
-Djna.debug_load.jna=true
-Dsun.io.useCanonCaches=false
-Djava.net.preferIPv4Stack=true
-XX:+HeapDumpOnOutOfMemoryError
After that restart your android studio and check bottom right side , One indicator is visible for memory usage. If you see that indicator shows more memory , than just click on that indicator its release unused memory from android studio and process will work smoothly.
After follow this step android studio will work smoothly.

Sluggish Android Studio Start up

I have Android Studio 3.0.1 with latest JDK installed on my i7 (4th Gen) dual core Win10 machine, 16GB RAM, 850 Pro 512GB SSD. But even with this beastly configuration, when double clicking on the Android Studio icon to launch the application, the software feels very sluggish in starting up. Takes approx. 15-20 odd seconds to just start up and then do the Gradle build of last opened app, which takes another 30-40 seconds.
Have set the vmoptions & gradle.properties to use -Xms2g and -Xmx4g along with parallel build, offline gradle execution and configureondemand.
Is there a way to drastically improve this performance when I have such a good machine configuration, probably tweaking some other Windows / Android Studio level parameters? Please help.
It start in seconds only because of that configuration.It takes few minutes to start in my laptop with 8gb ram.
So the time you mentioned seems pretty good.

Visual Studio 2017 Installation breaks Windows 10 (on a MacBook Pro)

I have a fresh Windows 10 installation on my MacBook Pro (Late 2016) along with the newest Bootcamp drivers. Everything is working and shiny up until now.
When I install Visual Studio 2017 Enterprise it works up to a point where the reboot takes place. This takes really long, but windows is starting again, for about 7 minutes windows boots while showing the loading indicator. When I'm finally prompted for Login, the MacBooks keyboard and trackpad doesn't work anymore, as we'll as I don't have a wifi connection or audio (having the x sign in taskbar).
I tried the whole painfull process three times now while ending up with the same problem. Windows is broken, which means I can't reinstall the bootcamp drivers (crashes system), no system restore points can be restored (failing), I can't reset windows (breaks the boot process and results in a blank screen). I guess this is somehow related to an intercompatibility between bootcamp and Visual Studio 2017.
I'm not sure if this is related to any specific components of VisualStudio which I install. I'll try a minimal install next...
It was the same for me, Windows 10 was loading 5-8 minutes and no keyboard and touchpad support. After 3-5 re-installs(windows and VS2017), found that issue caused by Hyper-V virtualization. It is disabled by default, but as soon as you installed VS 2017 with at least one component which require Hyper-V, you will never be able to login to you windows on macbook pro.
Just DO NOT install any emulators:
Google Android emulator,
Intel hardware accelerated execution manager(HAXM),
Visual Studio emulator for Android,
Windows 10 Mobile Emulator
And Windows will work fine.

Rendering error

Apologies for the generic title but I'm not sure how best to explain this one.
Visual Studio is rendering badly in a number of locations, notably the Quick Watch window, Unit Test Sessions window and the Unit Test context menu, see screenshot at the below url. It has been this way since I installed Visual Studio 2012, the OS at the time was Windows 7 and I upgraded to Windows 8 recently so it is not a Windows 8-specific issue.
This is Visual Studio 2012 on Windows 8 Pro. The machine is a Core i5 with 12GB of Ram running at 1% CPU and 3Gb of Ram used so it's definitely not a problem with lack of power, which is the only time I have ever seen any rendering faults like this.
I have tried a repair install and also uninstalling and re-installing Visual Studio but it has made no difference.
This issue occurs solely in Visual Studio 2012, not in any other applications on the computer nor on VS2010 when I had that installed.
Some frantic googling has revealed nothing and I am out of ideas.
Solution
Downloaded some old Vista/Windows 7 drivers from here which solved my problem.
The most likely culprit is the video drivers. I'd confirm by switching to the Basic VGA Display driver to rule out video driver issues.
If this fixes the issue, I'd look for different video drivers or report the problem to the card manufacturer.

Resources