[tustanivsky]

Summary

Sentry can now name the shader that caused a GPU crash, but only if it has the game's compiled shaders. Unreal Engine builds export them as .dxil files (one per shader, over ten thousand per game). This PR lets sentry debug-files upload upload them as dxil debug files and makes the upload path fast enough for sets of that size.

This is the toolkit version of getsentry/sentry-cli#3489, which was implemented earlier to test with the Unreal SDK which has not migrated to the Sentry toolkit yet (getsentry/sentry-unreal#1680).

Changes

• The scanner recognises a DXIL container by its header, before the files reach the object parser, which does not know shaders. The debug id is the 32-hex compiler hash the engine uses as the file name. dxil joins the --type list; --id accepts the bare file name or the hyphenated id. Shaders have none of the symbol/unwind/source features the other formats are filtered on, so those filters do not apply to them.
• The GPU crash decoder identifies a shader by NVIDIA's own hash of it, which only NVIDIA's Windows library can compute. The Sentry Unreal plugin computes it at build time and writes sentry-shader-manifest.tsv next to the shaders. The CLI reads that manifest once per directory and sends the hash and the shader group as the new code_id and shader_group assemble fields. Without a manifest the shader is uploaded without them.
• Assemble requests are sent in batches of a thousand files.
• Missing chunks are uploaded in batched requests, packed up to the server's chunksPerRequest and maxRequestSize limits, with a chunk shared by several files sent once. They were sent one request per chunk, so ten thousand small files took a lot of time.
• The assemble request is repeated right after the chunks are delivered, and the processing wait starts from that point. Before, the wait started before the upload; when the upload alone outlasted it, the command exited without the request that starts processing, and reported the files as not found or timed out although every chunk was on the server.

The last three points apply to every debug file type. Files that are not shaders otherwise take exactly the old path. debug-files find and check do not learn about shaders here.

Possible Follow-ups

Shader PDBs would add source file and line context to GPU crashes. They are left out for now because the server cannot use them yet, but the manifest already lists the PDB that belongs to each binary.

Related

• feat(teapot): Name the faulting shader of a GPU crash from uploaded DXIL binaries sentry#129684 adds the dxil debug file format and the assemble fields
• getsentry/teapot#22 names the shader from the binary
• Upload shader binaries for GPU crash symbolication after cook sentry-unreal#1678 exports and hashes the shaders after the cook
• feat(debug-files): Upload DXIL shader binaries sentry-cli#3489 is the legacy CLI version of this change

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
sentry-local	Skipped		Nov 4, 2026 3:07pm UTC

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 8e6a441. Configure here.}

[BYK]

Thanks a lot!