Skip to content

Commit 80cc692

Browse files
authored
feat(native): clarify filtering hook behavior in the context of fast-fail crashes... (#5524)
clarify filtering hook behavior in the context of fast-fail crashes when using crashpad on Windows together with the WER (Windows Error Reporting) module.
1 parent 943bb09 commit 80cc692

File tree

1 file changed

+6
-0
lines changed
  • src/platform-includes/configuration/before-send

1 file changed

+6
-0
lines changed

src/platform-includes/configuration/before-send/native.mdx

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -74,3 +74,9 @@ gradual migration from existing `before_send` implementations:
7474
The Crashpad backend on macOS doesn't currently support notifying the crashing process and thus can't correctly terminate sessions or call the registered `before_send` or `on_crash` hooks. It will also lose any events queued for sending at the time of the crash.
7575

7676
</Alert>
77+
78+
<Alert level="warning" title="Bypassed in Crashpad on Windows when capturing fast-fail crashes">
79+
80+
The Crashpad backend on Windows supports fast-fail crashes, which bypass SEH (Structured Exception Handling) primarily for security reasons. `sentry-native` registers a WER (Windows Error Reporting) module, which signals the `crashpad_handler` to send a minidump when a fast-fail crash occurs. But since this process bypasses SEH, the application local exception handler is no longer invoked, which also means that for these kinds of crashes, `before_send` and `on_crash` will not be invoked before sending the minidump and thus have no effect.
81+
82+
</Alert>

0 commit comments

Comments
 (0)