Capture system-level Xbox crashes (thermal, OS termination)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Xbox crash reporting via the GDK does not capture system-level crashes such as thermal shutdowns or OS-initiated process termination. These are surfaced by the Xbox platform OS and are not exposed to game middleware through current GDK APIs.
- Xbox SDK captures managed/native crashes within the game process via GDK
- OS-level signals (thermal events, kernel terminations) are not accessible to middleware
- Customers have no visibility into hardware-health-driven crashes
Investigate what GDK or Xbox system APIs expose for thermal/OS crash signals, and evaluate whether these can be captured as custom events or enrichment data via the Sentry Xbox SDK.
Reported by a gaming console customer (Triiodide Technologies).
Action taken on behalf of Richard Propst.
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
No files, tests, or entry points are named. Start by checking the Xbox GDK and platform APIs for thermal shutdown and OS-initiated termination signals, then review the Sentry Xbox SDK's custom-event and enrichment paths. Done means documenting the exposed signals and reaching a concrete feasibility outcome.
Written by the indexing model from the issue text.
Assessment
- Domain
- devtools, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100