Game: 6 seconds freeze entering castle town #2181
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#2181
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?
Longshot version
nightly-738-dd5ffe6a (source 8fd4dfe4)
Channel
Nightly
What kind of problem
Crash, freeze or black screen
What happened
Entering castle town freezes the game for about 10 s. This reproduced in both runs I logged. Presentation stops (0.2–0.3 fps over a 5–7 s window) and the game stops reading the controller.
Where in the game
Market_Child (child) Entering Castle Town
How often
Every time
Graphics card and driver version
AMD Radeon RX 6800, AMD proprietary driver 26.10.1 (AMD proprietary shader compiler)
CPU, RAM and operating system
13th Gen Intel(R) Core(TM) i7-13700 (24 threads), 32 GB, Windows 11 (build 26100)
Changes from the defaults
No response
longshot_log.txt
2 files below
Screenshots or video
No response
Before you send it
Possibly related, for context:
This is the simulated-turf stall that #2174 fixes, and the v3.1.0 release download does not have that fix.
Both of this issue's logs show it. On entering Market every simulated-turf list is released to 0 records. Then Market asks for a few, and they grow back from 0:
longshot_log.txt:blade list ... resized 40768 -> 0 records,pool ... resized 8608 -> 0and8128 -> 0(lines 18103–18202), thena capture's wait for write-back 198357 timed out,0.3 fps over the last 7.1 s,the game read no controller for 6.6 s, thenresized 0 -> 32/0 -> 64.longshot_log.1.txt: the same, at lines 10572–10818 (25536 -> 0... four write-back timeouts,0.2 fps over the last 5.6 s,0.3 fps over the last 7.1 s).That is #2174's sequence: each list grows back from 0 with a new write-back that a capture then waits 250 ms for. #2174 keeps the lists at the game's own size (143360 / 138240 records), so they can no longer reach 0. It merged after nightly-738, which this report ran, and it is in nightly-745 (
a2dc5385).A second report shows it on NVIDIA with the v3.1.0 release. It was made with the Insert menu's bug report, and was sent to me rather than posted. Windows 11, RTX 5070 (NVIDIA 621.24), i5-13600KF,
v3.1.0 (source 6f470170), in Market_Child:simulated turf: blade list ... resized 6208 -> 0 records,4864 -> 0, and the four pools to 0a capture's wait for write-back 121966 timed out (done 121960)andslow submit: 250.3 ms: dispatch 250.3, six timesnvn: GPU waits in 5 s: 32 sync waits (3498 ms),20.7 fps over the last 8.5 s, then0.5 fps over the last 6.0 s,the game read no controller for 6.0 s, then 37 and 56 fps, so about 25 s from the start before it ran near 60 fps againThe v3.1.0 release download was built from
9e10f6f7, one commit before #2174. Thev3.1.0tag points ata2dc5385. The release's owntarget_commitishis9e10f6f7. Recomputingnx2/version.py's fingerprint overgit archive <commit> host gpu nx2:9e10f6f7gives6f470170, the "source" that v3.1.0 printsa2dc5385gives63363428dd5ffe6agives8fd4dfe4, which matches nightly-738's line hereSo everyone on the v3.1.0 release can get this stall. Its worst case in #2174's own testing was
vk: FATAL: the GPU hung: no submission finished in 30 s, which players would see as a crash. Until the release is rebuilt, players can use nightly-745 or later, or putRX_VK_SIM_TURF_ADAPTIVE=0inlongshot_env.txt, which keeps the lists at stock as before #2093.Found with AI assistance (Claude Code).
From Discord:
Additional log from a player with Ryzen 9 9900X3D and RTX 5080: the log shows simulated-turf lists staying at stock sizes in Market and then adapting downward (e.g. 143360 -> 1920) after returning to ZoraFountain_Child; this differs from the zero-capacity/write-back timeout sequence diagnosed here. The log ends in a GPU hang, so please inspect the attached log for its exact trigger and version.
v3.1.1 is out with #2174: https://git.magicbean.dev/MagicBeanDev/Longshot/releases/tag/v3.1.1
It is built from
a2dc5385, the commit v3.1.0's tag names, so it has the simulated-turf fix that v3.1.0's download lacked. The stable channel offers it now, and launchers on v3.1.0 get it as an update. On a nightly, nightly-745 or later already has it.If the freeze on entering Market or going back into Hyrule Field still happens on v3.1.1, please post the new
longshot_log.txthere.For a maintainer with release rights: v3.1.1's page has no "What's new". Its notes cover the commits since v3.1.0's tag, and that tag is on the same commit. My account can push tags but not edit releases. This could go under its
## v3.1.1heading: