Game: Stack overflow crash while entering Hyrule Field #1919
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1919
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 and channel
v3.0.0 stable (source 87cb36aa); release channel.
What happened and steps
The game crashed while entering Hyrule Field. The attached crash record reports an unhandled exception,
0xc00000fd(stack overflow), on the Resource Control thread.Where in the game
Entering Hyrule Field (from which area is not specified).
How often
Not specified.
Graphics card and driver version
Not included in the crash record.
CPU, RAM and operating system
Windows is indicated by the crash-record format and
ucrtbase.dll; specific OS, CPU and RAM are not provided.Logs and crash record
Crash record attached below; full
longshot_log.txtwas not attached. The report provides no game log or graphics/system details.Still needed
Please add the full in-game bug report folder (especially
report.txtandlongshot_log.txt), the route/steps that led to entering the field and how often it happens, GPU and driver, and CPU/RAM/Windows version. The crash happened after 443 seconds of uptime; whether it is reproducible is unknown.Related reports
#809 covers a different crash in Hyrule Field triggered by opening and closing the map, on matching AMD Windows hardware; the trigger here is not established as the same problem. #1730 is an AMD 890M crash on the Hyrule Field-to-Kokiri Forest transition, also a different transition.
Files from the Discord report:
This crash record matches the first crash in #1772. It's v3.0.0 too, has
0xc00000fdon a game thread insideucrtbase.dll, and both stacks pass through the same frame,ucrtbase.dll+0x10bfb. In #1772 that "stack overflow" was really Windows' commit limit (RAM plus the page file) running out. A game thread's stack is only reserved, and Windows commits each page as the stack grows. At the limit it can't, so it raises a stack overflow with nearly all of the stack unused. Resource Control isn't a deep thread either.#1885 (ready for review) fixes that case: the thread waits for commit and goes on, as guest memory already does. Under a forced commit limit, main crashed this way in 2 of 3 starts and #1885 in none of 4.
To confirm this is the same crash, from the reporter if possible, @BeanIssues:
longshot_log.txtof that run. Lines likemem: commit of 0x... bytes at the commit limit made after ...orout of memorybefore the crash would settle it.Meanwhile, the likely workaround: let Windows manage the page file, or set it to at least 16 GB, and close other large programs while playing.
Posted by an AI agent (Claude Code) for d4nkn3ss.