Visual Studio with ReSharper is high on memory usage

Sometimes, Visual Studio with ReSharper can eat up more RAM than it should. This situation can be caused by several things, and here are some troubleshooting steps to determine the cause of it.

  1. Visual Studio configuration. Sometimes, memory issues can be caused by other extensions, which are installed in Visual Studio with ReSharper. It is a nice idea to temporary turn off or uninstall all other plugins/extensions, reload VS with ReSharper only and check memory usage after that.
  2. ReSharper configuration.
    1. Memory-heavy options. Several ReSharper features are known to use more memory when enabled. The most common feature is Solution Wide Analysis, which can use several hundred megabytes of RAM, especially on a big-sized solutions.
      Try to turn off Solution Wide Analysis (SWA) in "ReSharper | Options | Code Inspection | Settings", 'Analyze errors in whole solution' checkbox.
    2. Monitoring ReSharper Managed Memory. To enable this, please turn on the 'Show managed memory usage in status bar' checkbox located in "ReSharper | Options | Environment | General" dialog. This will indicate amount of RAM used by ReSharper.
      Please note, that you need to have the VS Status Bar visible to see the indication ("Tools | Options | Environment | General | Show status bar" checkbox).

    3. Manual Garbage Collection. Sometimes, CLR is not able to collect garbage automatically, and you can force a manual garbage collection. To do that, enable the 'Show managed memory usage in status bar' checkbox and described above and either double click on it, or right click and select the corresponding action.

  3. Verifying that the issues are caused by ReSharper. To do that, simply suspend ReSharper as described here and check if memory issues are still present.
  4. Perform a Memory Profiling. If none of the above helps, it is necessary to profile Visual Studio (with ReSharper enabled) process for memory usage. To do that, follow the instructions described here. After that, please create an issue in our YouTrack and let us know a short description of the memory consumption problems you're experiencing, and specify the name of your snapshot.

 

5 comments

I'm also having extreme problems with my VS2015+Resharper. I have 32GB of memory and sometimes nothing is left. Even if I close VS2015 the memory is not available again. Looking in the process manager I can also not see how consumes this large amount of memory. Do you know a way to find out who is using the memory?

 

Suspending Resharper also didn't help. 1GB was freed but not more.

1

ReSharper is using 1.15 GB of memory, according to the toolbar.  If VS were 64-bit, this would be a non-issue, but the IDE goes non-responsive while debugging (presumably because of memory fragmentation).  I'm disabling solution-wide analysis to see if that helps, but I have issues with being told to disable features to make the product usable.  My solution has < 20 projects; not what I'd consider a large solution.

2

Disabling solution-wide analysis does not help; nor does disabling most of my other extensions.  Forcing a garbage collect rarely frees up more than a megabyte or two.  ReSharper has once again become a memory hog, and I'm pretty sick and tired of having to kill devenv.exe because the IDE goes unresponsive when debugging due to being out of memory.

The issue is reminiscent of when JetBrains had a launch wrapper to handle memory management more efficiently... the virtual size is just under 4GB, but the actual physical memory being used is only about 2.5GB - seems like the issue is memory fragmentation more than anything.

1

I fully agree with James, we are really currently thinking of getting rid of Resharper. It causes more trouble than it's good. Since VS2017 has almost all the features we need, there no need to install Resharper anymore - so if nothing changes, we will switch to VS2017 immediately. We had bought 20 new licenses (the whole company has surely 1000) from JetBrains but there's no answer from JetBrains about this issue.

0

Wow, just installed VS 2017. Without ReSharper, my solution consumes around 400mb. With ReSharper enabled, it went to 2GB. I know it used to consume a bit more but in this state, is unusable. 

0

Please sign in to leave a comment.

Have more questions?

Submit a request