Game: Device-lost crash after receiving the Ocarina on Steam Deck LCD #1061
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#1061
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 a DM to the bot on Discord
Longshot version and channel
v3.0.0-rc.5 (source 92d0b2e1), release candidate.
What happened and steps
Game crashes with
reason: device lost; the reporter says crashes happen randomly while running in Kokiri Forest. Reproduced multiple times. They also report that the whole Steam Deck crashed once, without a crash record. They use Mako Frame Gen 5.0.Where in the game
Randomly while running in Kokiri Forest. Earlier report in this issue: immediately after Saria gave Link the Ocarina, as Link turned to run away.
How often
Repeated; the reporter says it was reproduced again and occurs randomly.
Graphics card and driver version
Steam Deck LCD; AMD Custom GPU 0405 (RADV VANGOGH), Mesa 26.2.0-devel (git-5c65d4fc31), from the attached full game log.
CPU, RAM and operating system
SteamOS 3.9.5, build 20261023.100, stable branch. Steam Deck LCD. Earlier crash report recorded AMD Custom APU 0405 (8 threads), 13 GB RAM; full log identifies the GPU and driver above.
Logs and crash records
The full
longshot_log.txtsupplied from desktop mode identifies Longshot v3.0.0-rc.5, the Steam Deck GPU/driver, 1280x800 output, and has 4,401 lines. Its FPS samples range from 9 to 192 (median 137); the late-session samples fall as low as 9 FPS. At the end, the log reports 14.5 FPS over the last 5 seconds, 44.2 ms GPU time per frame, and substantial GPU work and timeline waits. This is not a performance profile with the requested measurement environment variables, so more measurements would be needed to diagnose the slow portion.The attached crash record
crash-20261116T214748Z.txtreportsreason: device lost, threadsead::MainThread, uptime 144 s, andrecord_complete: yes. The screenshot shows a further complete device-lost crash record from v3.0.0-rc.5, uptime 144 s. Another screenshot notification says the graphics driver failed and suggests updating it and turning off overlays/tools hooked into the game.PR #670 improves reporting when a Vulkan timeline wait encounters device loss; it does not fix the underlying crash. That logging change is included in nightly-296-d9486a08 and v3.0.0-rc.5. The recent Kokiri Forest CPU-lock performance optimization, PR #766, is also already in v3.0.0-rc.5, but is a performance improvement and does not explain or fix this device-lost crash.
Still unknown
Exact steps/save context for the Kokiri Forest crashes, and whether they reproduce with Mako Frame Gen disabled. The reporter also reported a whole-Deck crash with no crash record. No measured performance profile was supplied for diagnosing the severe late-session FPS drops.
The existing third-floor Deku Tree crash report #1042 is a separate location/trigger.
Files from the Discord report:
From Discord:
Reporter says they were using FSR 3 at 50% render resolution, 720p output, Low settings on a Steam Deck LCD. They got through the Great Deku Tree, then crashed immediately after Saria gave Link the ocarina as Link turned to run away; after reboot they reached Hyrule but saw at most 9 FPS. Please request measured performance data and relevant settings for the Hyrule slowdown.
From Discord:
Follow-up from (Steam Deck; model/SteamOS, crash locations/triggers and reproducibility still unknown): v3.0.0-rc.5 crash records report
reason: device lost.crash-20261116T205308Z.txt: uptime 119 s, threadhost, backtrace includeslongshot_vk.so+0xa82908; image recordcrash-20261116T174801Z.txt: uptime 144 s, threadsead::MainThread.unclean-20261116T205015Z.txtsays ended without clean exit, not necessarily a crash. No full longshot_log.txt provided.Updated with more from Discord: Added SteamOS 3.9.5 details and random Kokiri Forest crashes; clarified PR #670 only changes device-loss reporting, not the underlying crash.
Files:
Updated with more from Discord: Added the complete v3.0.0-rc.5 game log and latest crash record, GPU/driver details, repeated Kokiri Forest crash reports and Mako Frame Gen 5.0; documented late-session FPS drop and the already-included PR #766 performance change.
Files:
From Discord:
Discord follow-up: the reporter says
longshot_log.txtwas empty in Gaming Mode, but later found logs after launching in Desktop Mode. The Desktop Mode screenshot shows a “Longshot closed unexpectedly” dialog: “What went wrong: The graphics driver failed. Update your graphics driver, and turn off overlays and tools hooked into the game.” Another screenshot shows a complete v3.0.0-rc.5 crash record (reason: device lost, uptime 144 s,record_complete: yes).From Discord:
Discord follow-up: the reporter says the crash occurs while standing in Kokiri Forest and also reproduces in Desktop Mode, not only Gaming Mode. The attached screenshot shows a complete v3.0.0-rc.5 crash record (
reason: device lost, uptime 144 s) and a crash notification stating: “What went wrong: The graphics driver failed. Update your graphics driver, and turn off overlays and tools hooked into the game.”Attachments from Discord:
crash-20261116T222543Z.txtandreport-20261116T222617Z.txt(from the message attachments), plus20261116_223226.jpg(the crash-dialog screenshot).From Discord:
Follow-up from the reporter: they disabled the Steam Overlay (Steam Library → Longshot → Manage → Properties → General → turn off “Enable the Steam Overlay while in-game”). They report no crash observed after 10 minutes; before disabling it, crashes occurred within seconds to at most 2 minutes. This is a promising workaround observation, not a confirmed fix; please keep the issue open pending longer-term confirmation.
From Discord:
Reporter follow-up: after updating to v3.0.0-rc.7 and playing for a couple of hours, they observed no further crashes. They suspect disabling the Steam Overlay was the effective change, noting they had also disabled it on rc.5. Because the update and overlay change are confounded, this is observational rather than confirmation of a specific fix.