Crashes are much more frequent in 2024.2

On windows. I regularly have one or more instances of rider open for most of the day. This usually isn't a problem - I would very rarely get any crashing. 

Since upgrading to 2024.2 last week, I've had at least two crashes per day, no messages are given before or after - it's just CTD with no information to help me navigate the problem. 

It usually happens when I'm debugging an asp.net core application. 

After crashing, syntax highlighting and autocomplete no longer work and I must invalidate the cache to make rider recognise code again. 

I'm going to have to revert to 2024.1 because it's so disruptive.
 

8
8 comments

I'm seeing exactly the same. 

Rider just freezes and never comes back. I check in Task Manager and I see Windows Problem Reporting writing out a 3GB file.

When its done, Rider shuts down. Takes about five minutes.

This is happening hourly, if not more. I'm going to have to revert.

JetBrains Rider 2024.2.1
Build #RD-242.20224.418, built on August 19, 2024
Subscription is active until September 10, 2024.
Runtime version: 21.0.3+13-b509.4 amd64 (JCEF 122.1.9)
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.awt.windows.WToolkit
Windows 11.0
.NET Core v8.0.4 x64 (Server GC)
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 3000M
Cores: 12
Registry:
 ide.experimental.ui=true
Non-Bundled Plugins:
 com.jetbrains.space (242.20224.155)
 nsubstitutecomplete-rider (2024.2.0)
 com.intellij.plugin.adernov.powershell (2.6.1)
 ru.adelf.idea.dotenv (2024.2.1)
 com.intellij.ml.llm (242.20224.421)
 com.intellij.bigdatatools.core (242.20224.419)
 com.intellij.bigdatatools.binary.files (242.20224.159)
 com.intellij.bigdatatools.rfs (242.20224.419)
 com.github.copilot (1.5.20.6554)
 me.rafaelldi.aspire (1.4.1)
 

4

With 2024.2 rider almost crashes every time I debug. It's almost unusable. Within the first 2-3 minutes of a debugging session, it completely hangs and then crashes.

I am on .net 8 and I have co pilot installed.

JetBrains Rider 2024.2.1
Build #RD-242.20224.418, built on August 19, 2024
Subscription is active until March 2, 2025.
Runtime version: 21.0.3+13-b509.4 amd64 (JCEF 122.1.9)
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Toolkit: sun.awt.windows.WToolkit
Windows 11.0
.NET Core v8.0.4 x64 (Server GC)
GC: G1 Young Generation, G1 Concurrent GC, G1 Old Generation
Memory: 4054M
Cores: 20
Registry:
 ide.experimental.ui=true
Non-Bundled Plugins:
 com.jetbrains.space (242.20224.155)
 com.github.copilot (1.5.20.6554)
 com.intellij.resharper.azure (4.0.2)
 

2

UPDATE: I've been using 2024.2.2 all day with no crashes. Fingers crossed!

1

Hello abann , Neil Finlay ,

Could you please let me know if the issue has been resolved for you using the bugfix as well? 

1

For me, Rider freezes instead of crashes. Sometimes it freezes when I close a window. Then I can't open a new instance of Rider. I first have to shutdown the process from task manager.

I still have the problem in 2024.2.3.

0

I get this problem, too. The Rider (even when I have two or three Solutions opened) freezes, and the only way to close it is by killing the process via Task Manager.

0

Hello Peter Hedberg, K Archimandritis

Thank you for the reports. Generally, crashes and freezes are caused for different reasons. 

First, I would like to ask you to install the latest 2024.2.4 Rider version. Then, if the issue persists, reach out via Help | Report a bug. The initial logs will be collected automatically and added to the issue privately. This allows us to take a closer look at your cases and help you to solve the problem. 

Thank you for your understanding! 

0

Happy to report that after moving to 2024.2.3 I was no longer getting the same problem.  I've since moved onto 2024.2.4 and still no issues. 

 

Cheers 👍

 

Edit: 

Spoke too soon. Rider is crashing again and after restarting will not correctly syntax highlight any file (.cs, .json or .feature files using reqnroll). I must invalidate caches to make it correctly highlight these types again.

0

Please sign in to leave a comment.