-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
feat(native): clarifying crashpad behavior #13689
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
Bundle ReportChanges will increase total bundle size by 243 bytes (0.0%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-client-array-pushAssets Changed:
view changes for bundle: sentry-docs-server-cjsAssets Changed:
|
docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx
Outdated
Show resolved
Hide resolved
a819d6e
to
6d9e389
Compare
docs/platforms/native/advanced-usage/container-environments/index.mdx
Outdated
Show resolved
Hide resolved
@@ -26,6 +28,9 @@ Currently, `crashpad` is the default on all desktop platforms because it | |||
* cooperation with Epic's Easy Anti-Cheat | |||
* CMake build scripts (some users use our backend handler forks solely because of this reason) | |||
|
|||
<Alert> | |||
When your deployment scenario should wait for the `crashpad_handler` to finish its work before a shutdown-after-crash (systemd, Docker), in Linux environments since SDK version [0.8.3](https://github.com/getsentry/sentry-native/releases/tag/0.8.3), you can enable the [option `crashpad_wait_for_upload`](/platforms/native/configuration/options/#crashpad-wait-for-upload) to delay application shutdown until the upload of the crash report is completed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When your deployment scenario should wait for the `crashpad_handler` to finish its work before a shutdown-after-crash (systemd, Docker), in Linux environments since SDK version [0.8.3](https://github.com/getsentry/sentry-native/releases/tag/0.8.3), you can enable the [option `crashpad_wait_for_upload`](/platforms/native/configuration/options/#crashpad-wait-for-upload) to delay application shutdown until the upload of the crash report is completed. | |
While your deployment scenario should wait for the `crashpad_handler` to finish its work before a shutdown-after-crash (systemd, Docker), in Linux environments since SDK version [0.8.3](https://github.com/getsentry/sentry-native/releases/tag/0.8.3), you can enable the [option `crashpad_wait_for_upload`](/platforms/native/configuration/options/#crashpad-wait-for-upload) to delay application shutdown until the upload of the crash report is completed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure about this change, I meant when
as in if
, since not all apps run into this problem (only when they are running in a systemd/docker env.)
docs/platforms/native/advanced-usage/container-environments/index.mdx
Outdated
Show resolved
Hide resolved
docs/platforms/native/advanced-usage/container-environments/index.mdx
Outdated
Show resolved
Hide resolved
docs/platforms/native/advanced-usage/container-environments/index.mdx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
- avoid it showing up under "When shouldn't I use the `crashpad` backend" in docs searches
Co-authored-by: Alex Krawiec <[email protected]>
fffffa2
to
9d2ff88
Compare
Vercel previews
DESCRIBE YOUR PR
(from Slack)
We already have some pages that detail aspects of this, but we want to make sure this is as clear as possible:
Current changes/fixes
repositioning
wait_for_upload
line in backend tradeoffs; otherwise, search showed it under "When shouldn't I use the crashpad backend?". Also added new heading above for it to fall under.(note: search doesn't seem to update right away)
after
(this is where I'd put a screenshot of the search pointing to
Why is crashpad the default
(preview) instead, but seems to not update on Vercel 🤔 )added min. version to
wait_for_upload
mentionadd docker entry point script to wait for handler (for people below 0.8.3/non-linux)
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.