Symptom
The "A Critical Failure Has Occurred" dialog appears in Rider on macOS. When this happens, the Rider .NET backend process (Rider.Backend) has terminated unexpectedly with a native crash, and Rider becomes almost unusable: code completion stops working, syntax highlighting is gone, and refactorings do not work.
Question
Rider crashes reporting the "Critical Error Has Occurred" error. How to collect the native macOS crash report (.ips) for the Rider.Backend process after a crash that cannot be reproduced on demand?
Answer
macOS automatically writes a native crash report (.ips) for any process that terminates with a native crash, including Rider.Backend. The report is generated for a crash that already happened, so it can be retrieved after the fact. This makes it the option to use when the crash is intermittent and cannot be triggered on demand.
When the crash can be reproduced, capturing a full crash dump via Rider backend crash. Linux/macOS/Windows. Capture crash dump using DOTNET_ env variables is preferred, because it captures both the managed and native stacks.
There are two ways to locate the report.
Option A: Console app
- Open the Console app (Applications | Utilities | Console).
- Select Crash Reports in the left sidebar.
- Find the entries named
Rider.Backendaround the time the "A Critical Failure Has Occurred" dialog appeared. - Right-click a matching entry, select Reveal in Finder, and collect the
.ipsfile.
Option B: Finder
The same reports are stored in ~/Library/Logs/DiagnosticReports/. In Finder, open Go | Go to Folder, paste the path, and collect the files that start with Rider.Backend and end in .ips.
If several reports match recent crashes, collect all of them.
Sharing the report
Upload the file or files to the JetBrains Uploads Service and share the Upload ID in the corresponding YouTrack issue or support request. The files can also be attached directly to the support request.
Related articles
- Critical Error Has Occurred" Rider Backend crash. How to capture crash dump (hub listing all capture methods per operating system).
- Rider backend crash. Linux/macOS/Windows. Capture crash dump using DOTNET_ env variables (preferred when the crash can be reproduced).
Comments
0 comments
Please sign in to leave a comment.