Fix: Prevent secondary panics during backtrace collection on Windows and handle minidump initialization failures #1379
+11
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes CAP-DESKTOP-T8. The issue was that: Secondary panic occurred in
backtrace::win64::tracewhile capturing stack for original panic, aborting process due to non-unwindable context.catch_unwindto prevent panics from propagating and log any initialization failures.This fix was generated by Seer in Sentry, triggered by Richie. 👁️ Run ID: 2575834
Not quite right? Click here to continue debugging with Seer.