"We've noticed that extension 'ReSharper Ultimate' is slowing Visual Studio" message

There are the following versions of the message:

2017-07-11_1339.png2017-07-11_1339_001.png

mstsc_2019-11-21_16-51-44.png

2017-08-17_1118.png

If you notice a real performance problem apart from that message, first of all, please try following this guide https://www.jetbrains.com/help/resharper/Speeding_Up_ReSharper.html

If those steps did not help and you still experience the performance problem, please follow https://resharper-support.jetbrains.com/hc/en-us/articles/207243205 article to send us a perf snapshot.

 

At the same time, we constantly work on ReSharper performance improvement, but some problems can only be solved by taking ReSharper out of the process. This is a massive architectural challenge and will take some time. The progress can be tracked here:
https://blog.jetbrains.com/dotnet/2018/05/28/introducing-resharper-performance-series/
https://blog.jetbrains.com/dotnet/2019/07/11/where-we-are-with-out-of-process-resharper/

53 comments
Comment actions Permalink

I can endure a slow startup, and I can even endure a little bit (NOT a lot) of slow typing. But there seems to be a particular issue at the moment related to slow typing that is worse than just slow typing. Basically, something is wonky with the queuing up of keystrokes and/or maybe the cursor position, such that when you type during the freeze, when it comes back and empties the keystroke queue, the results are in the wrong order, so you can't even type blind.

0
Comment actions Permalink

You know it’s bad, when Visual Studio even complains about the workmanship. And the fact, the proposed remedy is to hide that there is a problem.

Edited by Nick5454
1
Comment actions Permalink

Seriously, resharper is too fat, in most of time I have to reopen a project. I hope you have a lighter version because I rather have just searching file capability from resharper than a big fat slow rich features. 

Edited by Jerry27syd
0
Comment actions Permalink

Same issues since I can remember

0
Comment actions Permalink

After numerous complaints to jetbrains support, I have decided to suspend R# in most of the development work. I only use it once in a while doing code refactor and cleanup. 

0
Comment actions Permalink

I think there is an issue with long methods. Writing code near the end of a particularly long method (~1000 loc?) causes regular extremely long freezes, sometimes 10-30 seconds or more. You can see the method signature intellisense popup appear blank and in the wrong place (near the top of the screen instead of near the cursor, but who knows if that's related or not.

0
Comment actions Permalink

It's really a fact: most developers are aware of the fact that on one hand Resharper can be a great tool, but it often blocks your progress instead of increasing it, and increasing it is the whole point of having a tool like Resharper.

Example:
I just upgraded to Resharper 2019.2 (using VS 2017) and my experience is that I regularly need to wait a few seconds after typing a fragment of code.

Also regularly it just makes VS hang: a wait cursor shows and in the end I have no choice than to kill VS and start again.

It was already bad before the upgrade, but it has become worse. Especially the total hanging of VS is new.

Unfortunately, the link you provided to speed up resharper is dead (gives 404), so not useful to me

2
Comment actions Permalink

Hello Joepwijers,

Thank you for your feedback.
To begin with, I've updated the link to speed up ReSharper guide, so it's correct now.

We do understand there's a performance problem and we are working on it. A big part of the problem we have is that recent versions of Visual Studio have very much increased the amount of memory they use. That leaves less memory that ReSharper can use, and because VS is 32 bit, if the project is large enough, it can start to hit the limits where the garbage collector kicks in, and performance starts to suffer. 
We have been working on moving ReSharper out of the process for a long time; here you can see the latest updates: https://blog.jetbrains.com/dotnet/2019/07/11/where-we-are-with-out-of-process-resharper/.
Still, as we are very interested in improving performance we need to determine the cause of the problem in every single case.
Could you please provide a performance snapshot as described in the article. Please specify the steps that lead to the problem in the snapshot details.
We'd be really grateful for the assistance.

 

Edited by Angelina Elycheva
0
Comment actions Permalink

I was using VS 2017 and had to remove Resharper as it was unusable, Having removed it, Its been much easier to live without it than I thought.
I have now upgraded to VS 2019 and working the same projects, VS 2019 feels much faster, hopefully this means Resharper has half a chance of running better on VS 2019 but I am not going to risk re-enabling my subscription to be disappointed..again. 

2
Comment actions Permalink

Angelina, I have noticed with the 2019.2 build that ReSharper is MUCH BETTER NOW as far as freezing up Visual Studio.  I have actually re-enabled it again.  :)

-1
Comment actions Permalink

2019.2 C++ is still unusably slow here, not just during start but everywhere.  VS constantly freezes with it enabled, even opening a simple header can take upwards of a minute, scrolling is atrocious, text entry goes from merely feeling slightly sloppy and compared to Notepad++ to noticeably lagging and even frequent freezes, debugging is almost unusable even after disabling the various visual "helpers" that try to tell you the contents of every variable on screen, every single step on moves at the speed of molasses, again it can take minutes to step in/on/over/out for a single line, then on top of that the UI itself crashes frequently.

I really want to have R# installed and running because it's features are awesome, but it just slows things down waaaay too much and makes VS too unstable for me so I can't justify it.  I really hope that the large scale back-end restructuring they talked about doing in a recent blog post will deliver dramatically improved editor responsiveness and stability for editing and debugging.  Honestly the time it takes VS to launch was never a concern, that other stuff though actually affects my ability to be productive.

1
Comment actions Permalink

VS is super laggy with ReSharper enabled. It's unbearable. I am getting these microstutters and freezs all the time making it impossible to work with this tool. I will convince my company to abolish ReSharper in favor of something more stable. All they tell you is to submit performance profiles, acting like it's my machine that is causing the issues. Do you actually test your product on large code bases?

0
Comment actions Permalink

>>Angelina, I have noticed with the 2019.2 build that ReSharper is MUCH BETTER NOW as far as freezing up Visual Studio.  I have actually re-enabled it again.  :)

Can anyone let us know if this is indeed the case? I have given up on Resharper a while ago while struggling through it...currently managing with codemaid, roslinator and intellisense extender. 

I would love to buy a 2019 subscription if this works again! I work mainly with asp.net and c# and have about 20 projects each has hundreds of files. 

Actually it was not me but my vs.net 2017 gave up on the ReSharper :)

Edited by SK Dutta
0
Comment actions Permalink

In case it's useful to anyone, some severe slowdown that I struggled with for a couple of years turned out to be related to the Solution Explorer object nodes. (The tree nodes that show you types, methods and properties right in the Solution Explorer.)

The symptom was tons and tons of 5+ second delays while typing, and it primarily occurred when adding members to a type. Typing in a (small) method body for the most part had little to no issues, but adding properties to a class, *that* definitely did. I loathed having to type out a bunch of properties because of all the pauses.

When I finally realized it was *changing the structure of a class* that seemed to be where the issues were caused, I realized it might be related to the Solution Explorer updating its nodes. I installed the "Disable Solution Explorer's Dynamic Nodes" extension from Mads Kristensen and the problem finally went away. It was so much better to finally be able to type without constantly stalling.

1
Comment actions Permalink

I realy loved resharper, but the performance is getting worse with every update. will try without resharper and use features of vs. 

1
Comment actions Permalink

- 10 seconds lag on just opening the empty solution

Looks like there is no any feedback for a long time. Thats sad.

Edited by Muletail
1
Comment actions Permalink

The problem that I have is a showstopper. I tried to deactivate everything ReSharper recommends, but the main problem is the memory. The src/Kephas.sln solution with 66 projects (https://github.com/kephas-software/kephas) will take approx. 600 MB without ReSharper and 2.3 GB with ReSharper, which makes development practically impossible. And another thing: I use also the StyleCop ReSharper add-in. From what I know, there are 3 code analyzers that get loaded: Roslyn, ReSharper, and StyleCop. This is insane, but I don't know how this can be optimized. From what I know, Resharper does not integrate with the StyleCop Analyzers, to remove at least the StyleCop overhead.

My only practicable solution was to deactivate ReSharper :(.

P.S. I use Visual Studio 2019 (16.2.3), with ReSharper 2019.2.2.

Edited by Ioan Crișan
0
Comment actions Permalink

I am having problems slowing down VS2019. When I try to disable the resharper VS it asks for a reboot, but after the reboot I find resharper magically enabled again. The only way to disable the resharper is to uninstall it.
I had previously stopped using the resharper from vs2017 because it slowed down the work too much, but I thought it was caused by the poor performance of my PC. Now with a double Xeon and 12 GB of RAM VS2019 it is again incredibly slowing down. Too bad because the product would be very useful, but obviously it is badly developed. Fortunately, today many resharper features can be achieved by installing individual add-ons, and many are integrated directly into VS.

Edited by Edika
0
Comment actions Permalink

I can only join the long list of unhappy customers.

Using Resharper 2019.2 on Visual studio 2019 and 2017 is completely useless, the performance is atrocious.

Our solution is rather big with 185 projects, but VS runs significantly faster without Resharper.

We experience memory problems, "not responding" Visual Studio and crashes.

Are you trying to push people into running Rider? (that runs fine with 185 projects)

0
Comment actions Permalink

I also regularly get the message "We've noticed that extension 'JetBrains ReSharper Ultimate 2019.2.2' is slowing typing performance." in VS 16.2.3 - and the editor is, in fact, frozen, I cannot type for a second or two. So *something* is definitely slowing down typing performance - either R# or VS itself. It seems unlikely to me that VS would incorrectly blame an extension for this.

1
Comment actions Permalink

For some time, I blamed the bad performance of R# on my old computer, and running VS in a VirtualBox.

Reading all of the comments here, I can postpone buying a new machine, because it won't help me.

Thanks for all the reports. I'll join the list of people waiting for Jetbrains to fix the issue.

0
Comment actions Permalink

Really it was a waste of money to buy it because I have to disable it all the time. It seems they don't do anything about it because they might soon be going to discontinue further development anyway.

1
Comment actions Permalink

Another voice for performance as a feature!!!

0

Please sign in to leave a comment.

Have more questions?

Submit a request