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.


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:
    2. Latest Early Access Program (EAP) builds are available here:
    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):
  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.