Knowledge Base/ReSharper FAQ/Troubleshooting

Visual Studio with ReSharper is freezing and/or crashing

Alex Berezoutsky
posted this on July 10, 2013, 17:31

Since ReSharper is integrating within Visual Studio deeply, there are some scenarios, some specific configurations, solutions or use cases, which may lead to freeze or crash of Visual Studio with ReSharper. This article guides through troubleshooting steps in order to fix or avoid the crash, or at least determine the cause of the issue.

There are several types of VS crashes:

  • Unhandled exception, like 'System.OutOfMemoryException'.
  • Microsoft Visual Studio has encountered a problem and needs to close.
  • Microsoft Visual Studio (Not Responding) 'white screen' freeze.
  • Silent crash. In case of silent crash, VS does not show any error messages, warning windows, etc.

screen505_5.png

Despite these three cases are different, here are some common steps to troubleshoot the crash:

  1. Hardware and OS Configuration.
    1. VS can crash because of the PC hardware and OS - for example, System.OutOfMemoryException is known to be present on Windows XP 32-bit environment with low RAM amount. In most cases it cannot be avoided, so please make sure that you're using a modern OS with 64-bit architecture - like Windows 7 x64 or Windows 8 x64.
    2. As for the 'System.OutOfMemoryException', there are some workarounds, which can possibly help to deal with it. You're welcome to try out the solution described in this article.
  2. VS configuration
    1. ReSharper may conflict with the other Visual Studio addins and extensions, so it is a nice idea to launch Visual Studio in safe mode to turn off all installed extensions and temporary disable/uninstall them one-by-one. This will allow to check whether there's a conflict between different extensions, which makes VS to crash.
    2. If the crash occurs on VS startup with direct solution opening, try to launch VS itself (e.g., just click on the VS desktop shortcut to start the Visual Studio, not a *.sln file of the solution you're working with).
    3. Sometimes, Visual Studio and/or .NET Framework itself can be corrupted or damaged, so launching the 'Repair' action on Visual Studio installation (via 'Control Panel | Add/Remove Programs') can help in this case.
  3. Solution configuration.
    1. To make sure that the crash is solution-specific, please try to create new solution (like, C# Console Application) and check if the crash is still present.
    2. If the crash seems to be a solution-specific case, please try to remove ReSharper caches and *.suo file as described here and check if it helps to resolve the issue.
  4. ReSharper installation. Since we do our best in terms of fixing issues and bugs, it is a nice idea to check if you're using the latest ReSharper version available.
    1. Latest release version is always available here: http://www.jetbrains.com/resharper/download/index.html
    2. Latest Early Access Program (EAP) builds are available here: http://eap.jetbrains.com/resharper/
    3. If you're licensed to an older version, check that you're using the latest version in the corresponding major branch (for example, 6.1.1 is the latest version for the ReSharper 6.x): http://resharper-support.jetbrains.com/entries/21206508
  5. Crash reproduction. If the steps above do not help, please try to narrow down the cause of the issue:
    1. Determining what exact action (f.e., 'Open Solution', 'Go To Type', 'Expanding Live Template', etc.) is making VS to crash.
    2. If this issue is solution-specific, please try to 'crop' the solution (e.g., remove files, references, etc.) to make the solution smaller in size, but still with this issue reproducible - in some cases, it might be even a single file, which is causing the issue.
    3. After acquiring as much information as possible, please contact JetBrains ReSharper Support Team using the 'Submit a request' form above and letting us know about the issue with detailed description. Our team will guide you and provide further steps to troubleshoot the issues.
 

Comments

User photo
Dsinger

Hi, 

When I build my solution it takes it 10 minutes(!) to start responding again. 

If i build while R# is disabled it runs without any issues. 

I am using R# 9.0

Got any idea what I can do to resolve this issue?

March 9, 2015, 17:35
User photo
Jr

We have the same problem Dsinger has.

I am using R#9

JetBrains ReSharper Platform 6 Build 6.0.20141219.120158 on 2014-12-19 12:56:02Z
JetBrains ReSharper 9.0 Update 1 Build 9.0.20141219.130142 on 2014-12-19 13:12:31Z

Application Packages:
EtherealCode ReSpeller build 4.0.0.0-alpha2 on 2015-02-11 09:53:00Z.
JetBrains Fake VisualStudio VsPackageAssembly build 12.0.0.0 on 2015-02-11 09:53:13Z.
JetBrains Platform Core Ide build 6.0.20141219.120158 on 2014-12-19 12:56:02Z.
JetBrains Platform Core Shell build 6.0.20141219.120162 on 2014-12-19 12:53:09Z.
JetBrains Platform Core Text build 6.0.20141219.120158 on 2014-12-19 12:56:02Z.
JetBrains Platform Installer build 6.0.20141219.120158 on 2014-12-19 12:56:02Z.
JetBrains Platform Symbols build 6.0.20141219.120158 on 2014-12-19 12:56:02Z.
JetBrains Platform VisualStudio build 6.0.20141219.120158 on 2014-12-19 12:56:02Z.
JetBrains Psi.Features ExternalAnnotations build 9.0.20141219.130140 on 2014-12-19 13:00:40Z.
JetBrains Psi.Features SolutionBuilder build 9.0.20141219.130140 on 2014-12-19 13:00:40Z.
JetBrains Psi.Features src build 9.0.20141219.130140 on 2014-12-19 13:00:40Z.
JetBrains Psi.Features Tasks build 6.0.20141219.130140 on 2014-12-19 13:00:40Z.
JetBrains Psi.Features VisualStudio build 9.0.20141219.130140 on 2014-12-19 13:00:40Z.
JetBrains ReSharper src build 9.0.20141219.130142 on 2014-12-19 13:12:31Z.

Visual Studio 12.0.31101.0.

We use 2 solutions, 1 for client and one for server and use WCF.

Our client doesn't have any problems building, but our when we build the server the first time it freezes visual studio for +10 minutes.

The next build on the server works fine.

IF I however changes anything in web.config, then resharper does the same thing. It builds fine, waits a little while, then freezes visual studio for 10+ minutes. It works fine with R# turned off. I don't understand why resharper should do anything that freezes visual studio and makes it not responding, why not just make the work in the background - whatever it is?

Have you heard about this before and do you have any work arrounds? What could be likely culprits in R#, I can turn off? As it is right now we can't use R#9.

I didn't have this problem in vs2010 with R#6.

March 13, 2015, 13:23
User photo
Jr

I tried turning Enable code analysis off, but the problem is still there. Solution wide analysis is also turned off.

March 13, 2015, 13:39
User photo
Jr

I just tried installing R# 8.2.3. Instead of freezing 10+ minutes after change of web.config and rebuild, this version only freezes 15 seconds.

I can reccommend everyone uninstalling R#9 and using R# 8.2.3 until this issue is fixed.

March 13, 2015, 14:09
User photo
Rclarke

Having a similar issue, well a number of my colleagues are, with R#9.

We have a large solution (152 projects ... don't ask, it's not my fault!!) and basically, build actions often cause a white screen death of Visual Studio. Most notably when building the entire solution but it also hangs offtimes if we're attached to an IIS process.

If we temporarily suspect R# then this stops.

When it's hanging, I've used Process explorer and the thread that's locked is maxing out a core, and appears to always be stock on a MutexLock.

My manager is urging us to go back to R#8 but I love the new features and only want to do this as a last resort.

Please help us!

March 25, 2015, 11:15
User photo
Dsinger

Hi Rclarke, 

I downgraded to the previous version of R# as suggested above, but if you want to still use R# 9 you can download an EAP version.

Heres a link: 

https://confluence.jetbrains.com/display/ReSharper/ReSharper+9.1+EAP

March 25, 2015, 11:19
User photo
Angelina Elycheva
JetBrains

Everyone experiencing freezes during build process  please try ReSharper 9.1 EAP builds  as @Dsinger suggested in previous message.

March 25, 2015, 12:07
User photo
Rclarke

Thanks, I'll give this a try.

March 25, 2015, 12:09
User photo
Zak Mindbender

I too have problems with crashing VS2013 with R# 9.  Just starting makes it crash. even without openning any sln files

April 2, 2015, 20:37