Game: Repeatable device-lost crash 1–20 seconds after Alt+Tab on RX 9070 XT #1376
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1376
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Reported on Discord
Longshot version
Nightly-403 (reporter says same commit as RC7).
Channel
Nightly.
What happened and steps
Longshot crashes with a device-lost error after switching away from the game with Alt+Tab. The reporter says the crash is 100% reproducible, with a delay of about 1–20 seconds after Alt+Tab. The AMD driver does not restart. The reporter says the in-game location does not matter; the attached log places the game in Hyrule Field.
Where in the game
Reported location-independent; log indicates Hyrule Field.
How often
Every time (100% reproducible).
Graphics card and driver version
AMD Radeon RX 9070 XT, AMD driver 26.10.1.
CPU, RAM and operating system
Intel Core i5-13600K, 32 GB DDR4, Windows 11.
longshot_log.txt
The reporter attached
longshot_log.txt(7.2 MB). Relevant lines:Still unknown
Exact Alt+Tab sequence (including fullscreen/windowed state), graphics settings, and Windows build. The attached log should be reviewed for complete system/settings details.
PR #1220 adds a diagnostic checkpoint for device-lost reports; its description explicitly says it does not fix device-lost crashes. It is not a fix for this report.
Files from the Discord report: