"Critical Error Has Occurred" Rider Backend crash. How to capture crash dump

Question

Rider reports a "Critical Error Has Occurred". Support team requests a crash dump. How to capture it and share it?

Answer

Depending on OS follow the below instructions. If there are several instructions per-os, follow the first one. In case the dump doesn't generate, try the next available option.

Windows:

1. Rider backend crash. Windows. Capture crash dump using Windows Error Reporting
2. Rider backend crash. Linux/MacOs/Windows. Capture crash dump using DOTNET_ env variables

MacOs:

1. Rider backend crash. Linux/MacOs/Windows. Capture crash dump using DOTNET_ env variables
2. Rider backend crash. MacOs. Crash produced by system 'ulimit -c unlimited
3. Rider backend crash. MacOS Arm64. Collect Managed Call Stack for the hanged or crashed Rider.Backend process
4. Rider backend crash. macOS. Collect the native crash report (.ips) when the crash cannot be reproduced

Linux:

1. Rider backend crash. Linux/MacOs/Windows. Capture crash dump using DOTNET_ env variables
2. Rider backend crash. Linux. Crash produced by system 'ulimit -c unlimited