From d3f06f59aeb9280304c92c089a8dab777b70a16c Mon Sep 17 00:00:00 2001 From: Ivan Tustanivskyi Date: Wed, 26 Aug 2026 11:10:20 +0300 Subject: [PATCH] Document Unreal thread stackwalk mode setting Covers the new native backend setting that limits client-side stackwalking to the crashed thread. --- .../unreal/configuration/native-backend/index.mdx | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/platforms/unreal/configuration/native-backend/index.mdx b/docs/platforms/unreal/configuration/native-backend/index.mdx index 100ab7284d4454..804311581f3914 100644 --- a/docs/platforms/unreal/configuration/native-backend/index.mdx +++ b/docs/platforms/unreal/configuration/native-backend/index.mdx @@ -49,6 +49,18 @@ Available modes: - `NativeStackwalking` - Walk the stack client-side in the crash daemon and send a JSON event with stack traces. No minidump is generated, resulting in faster uploads and smaller payloads. - `NativeStackwalkingWithMinidump` (default) - Perform client-side stack unwinding and also attach a minidump for deep debugging when needed. +### Thread Stackwalk Mode + +Controls which threads have their stack walked client-side. You can adjust this in **Project Settings > Plugins > Sentry > General > Native > Thread stackwalk mode**. + +Available modes: +- `CrashedThreadOnly` - Walk the crashed thread only. The remaining threads are still reported with their id and name, but without a stack trace. +- `AllThreads` (default) - Walk every thread of the crashed process, providing the most context. + +Walking every thread of an application with a high thread count, such as an editor build, can noticeably delay crash processing. Switching to `CrashedThreadOnly` keeps the crashed thread's stack trace intact while shortening the time needed to collect a crash. + +This setting applies only when client-side stack unwinding is enabled, i.e. when the crash reporting mode is `NativeStackwalking` or `NativeStackwalkingWithMinidump`. + ### Enabling Network Access on macOS