Game: Crash on Steam Deck LCD on third floor of the Great Deku Tree #1042
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#1042
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 by bustylass338 in a DM to the bot on Discord
Longshot version and channel
nightly-322-5bc54c6c (source 4527e8a8), nightly.
What happened and steps
Longshot closed unexpectedly while playing. The player reports reaching the third floor of the Great Deku Tree before the crash; exact actions immediately preceding it are unclear.
Where in the game
Great Deku Tree, third floor.
How often
Not provided.
Graphics card and driver version
Steam Deck LCD, AMD Custom GPU 0405 (RADV VANGOGH), Mesa 26.2.0-devel (git-5c65d4fc31).
CPU, RAM and operating system
AMD Custom APU 0405 (8 threads), 13 GB RAM; SteamOS Linux 7.2.7-valve2-2-neptune-72-g31504582a073, KDE/Wayland.
Changes from defaults
Crash report records output resolution 1280x720 and handheld profile enabled; the full settings are in the attached report.
Crash details
Unexpected error after 797 seconds; fatal signal 11 on PlacementMgr thread. The log ends with a read exception at
longshot+0x7c2e40c.longshot_log.txt
Attached session log.
Still needed
Whether/how often it reproduces, exact actions immediately before the crash, and whether a particular save or route is involved.
Files from the Discord report: