Rider backend crash. Linux/macOS/Windows. Capture crash dump using DOTNET_ env variables

Symptom

At some point the "A Critical Failure Has Occurred" dialog appears. When that happens, Rider becomes almost unusable: completion stops working, syntax highlighting is gone, refactorings don't work, etc:

Question:

How to capture a crash dump of Rider.Backend using DOTNET_ environment variables?

Answer:

1. Open terminal:

2. Set the following environment variables:

   1. macOS/Linux terminal:

      export DOTNET_DbgEnableMiniDump=1
      export DOTNET_DbgMiniDumpType=4
      export DOTNET_DbgMiniDumpName=/tmp/rider_crash.%d.dmp
      export DOTNET_EnableCrashReport=1
      

   2. powershell:

      $env:DOTNET_DbgEnableMiniDump=1
      $env:DOTNET_DbgMiniDumpType=4
      $env:DOTNET_DbgMiniDumpName="C:/JetDumps/rider_crash_net.%d.dmp"
      $env:DOTNET_EnableCrashReport=1
      

3. Start Rider using the same terminal, so Rider inherits the environment variables set.

   cd {RiderInstallDir};
   ./Rider{version}.app/Contents/MacOS/rider # MacOs
   ./bin/rider64.exe # Windows
   ./bin/rider.sh # Linux
   

4. Reproduce the issue. The memory dump should be automatically saved as the specified path (/tmp/rider_crash.%d.dmp. A crash report whose name matches the dump path, or whose name is appended with .crashreport.json, should also be generated.

5. Archive the generated file;

6. Upload the archive to the Uploads Service and share the Upload ID (shown at the end of the upload process) in the corresponding YouTrack issue, Support request or thread.

Reference: Collect Dumps on Crash - .NET | Microsoft Learn