From b67ac2ae526ca84fae862170d2ed16aa74eff219 Mon Sep 17 00:00:00 2001 From: Mischan Toosarani-Hausberger Date: Wed, 28 May 2025 20:17:34 +0200 Subject: [PATCH 1/3] feat(native): reflect windows support for crashpad-wait-for-upload in backend tradeoffs --- .../platforms/native/advanced-usage/backend-tradeoffs/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx b/docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx index 0a805eb7de21a..97a27843bf8aa 100644 --- a/docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx +++ b/docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx @@ -29,7 +29,7 @@ Currently, `crashpad` is the default on all desktop platforms because it * CMake build scripts (some users use our backend handler forks solely because of this reason) -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. +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), in Windows environments since SDK version [0.8.6](https://github.com/getsentry/sentry-native/releases/tag/0.8.6), 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. ### When shouldn't I use the `crashpad` backend? From 7afaab78c566c4185d6ef719d05466366f4aab38 Mon Sep 17 00:00:00 2001 From: Mischan Toosarani-Hausberger Date: Mon, 2 Jun 2025 22:48:32 +0200 Subject: [PATCH 2/3] Update docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx Co-authored-by: Alex Krawiec --- .../platforms/native/advanced-usage/backend-tradeoffs/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx b/docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx index 97a27843bf8aa..d0130a745ccf7 100644 --- a/docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx +++ b/docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx @@ -29,7 +29,7 @@ Currently, `crashpad` is the default on all desktop platforms because it * CMake build scripts (some users use our backend handler forks solely because of this reason) -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), in Windows environments since SDK version [0.8.6](https://github.com/getsentry/sentry-native/releases/tag/0.8.6), 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. +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), and Windows environments since SDK version [0.8.6](https://github.com/getsentry/sentry-native/releases/tag/0.8.6), 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. ### When shouldn't I use the `crashpad` backend? From 781a95c4384662fb26f3f8f27c268921fe7fcaf4 Mon Sep 17 00:00:00 2001 From: Mischan Toosarani-Hausberger Date: Thu, 5 Jun 2025 21:57:02 +0200 Subject: [PATCH 3/3] update actual version tag --- .../platforms/native/advanced-usage/backend-tradeoffs/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx b/docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx index d0130a745ccf7..ced2a9443bef8 100644 --- a/docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx +++ b/docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx @@ -29,7 +29,7 @@ Currently, `crashpad` is the default on all desktop platforms because it * CMake build scripts (some users use our backend handler forks solely because of this reason) -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), and Windows environments since SDK version [0.8.6](https://github.com/getsentry/sentry-native/releases/tag/0.8.6), 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. +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), and Windows environments since SDK version [0.9.0](https://github.com/getsentry/sentry-native/releases/tag/0.9.0), 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. ### When shouldn't I use the `crashpad` backend?