Support ingestion and processing of GPU crash dumps
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Problem Statement
Graphics-heavy applications produce a class of failure that CPU-side crash dumps
cannot explain: device removal, driver resets, and GPU-side faults. Vendor tooling
produces its own dump artifacts for these, containing GPU state, the faulting shader
or draw call, and driver context at the time of failure.
Sentry ingests CPU minidumps and symbolicates them well. GPU dumps have no ingestion
path, so the crashes that most often make an application unusable on a specific
hardware and driver combination are the ones with the least information in the crash
tool.
In practice this means:
- GPU faults present in the CPU stack as a generic device-lost or driver error, with
no indication of the underlying cause. - Teams cannot correlate GPU faults with driver version, GPU model, or graphics API
version at scale, so they cannot distinguish a widespread driver regression from
an application bug. - The dumps are already produced client-side. They simply have nowhere to go.
This is particularly acute for teams shipping to a wide consumer hardware surface,
where testing every driver and GPU combination is not possible and post-release
telemetry is the only realistic way to find these failures.
Solution Brainstorm
- Accept GPU crash dumps as a first-class attachment type with dedicated parsing,
rather than as an opaque blob. - Surface the GPU-side fault context on the event alongside the CPU stack trace.
- Support grouping and search on GPU fault attributes such as driver version, GPU
model, and faulting shader, so a driver-specific regression appears as one issue
rather than scattered across many.
Product Area
Issues
Requested by Saad Khan.
--
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by tracing the existing CPU minidump ingestion, attachment processing, and event grouping/search paths. Done would require an agreed design and implementation that accepts GPU dumps, exposes their fault context, and supports grouping or search by the requested GPU attributes.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100