Editor Version 2021.3.17f1 — JetBrains Rider Editor – Version 3.0.20
This morning I installed the new rider package from 04-05-23. Ever since then after I press play, the Editor goes to high cpu usage and stays there. My Unity editor will remain with high cpu and bad performance no matter what I do. I can press play and run editor builds over and over and it has very low FPS and my operating system shows that unity editor is using high cpu.
If I close rider, everything goes back to normal and things work fine…
If I do open C# project again, one build will work fine and then I go back into the broken state.
I believe that Rider plugin [3.0.20] has a bug with editor [2021.3.17f1].
Does anybody else have this issue? Hopefully this helps someone else.
Thank god someone else is talking about this. I have the same issue. How do I downgrade a package? all the other threads where people ask get met with “why would you want to do that”. I really can’t have this today. Got a lot of work to do!
I am on Windows 11 with Unity Editor Version 2021.3.17f1
I could try other versions of Editor later this evening if that would help. Its pretty easy to reproduce as of right now and I heard from a couple other people that they also hit this issue. Luckily rolling back isnt too difficult.
Open the profiler and press record. With the Rider 3.0.20 extension installed you will see lots of busy and slow things. Lots of big yellows. After you revert back to Rider 3.0.18 this goes away and the profiler is nice and quiet.
Also with Rider 3.0.20 extension installed, if you open task manager in windows you will see that Editor is always using 1 cpu core at 100% when Rider is open. If you close Rider or roll back to the 3.0.18 extension the cpu is very minimal. On mac you could probably witness the same thing with htop.
I also had the same problem described above (update caused Unity performance to tank). Am on Unity 2022.2.5. Have changed back to 3.0.18 and everything is fine again
For the time being, it might be easier for you guys to change the manifest version from 3.0.20 to 3.0.18, seems to be fixed, and you probably dont need to be on the bleeding edge of this rider plugin any way
I too confirm that rolling back com.unity.ide.rider to 3.0.18 has improved performance. Using Unity 2021.3.23.
However, I use PlasticSCM integration with Rider as well which has terrible performance anyway. So it’s a bit hard to tell at times.
