Game: Stack overflow crash while entering Hyrule Field #1919

Open
opened 2026-11-20 21:21:26 +00:00 by BeanBot · 2 comments
Member

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.txt was not attached. The report provides no game log or graphics/system details.

Longshot crash record 1
version: v3.0.0 (source 87cb36aa)
run_id: bef282d22d5553ab0f1087af85d197dd
when: 20261120T205435Z
uptime_s: 443
reason: unhandled exception
thread: Resource Control
module_offset: ucrtbase.dll+0x5b96
last_present_age_ms: unknown
log: longshot_log.txt
pid: 9572
started: 20261120T204712Z
signal: 0
signal_code: 0
exception: 0xc00000fd
fault_address_class: other
host_backtrace_method: Windows unwind
host_backtrace: ucrtbase.dll+0x5b96
host_backtrace: ucrtbase.dll+0x4f24
host_backtrace: ucrtbase.dll+0x4dcd
host_backtrace: ucrtbase.dll+0x443d
host_backtrace: ucrtbase.dll+0x112d9
host_backtrace: ucrtbase.dll+0x10d9e
host_backtrace: ucrtbase.dll+0x10bfb
host_backtrace: longshot.exe+0x1da9bead
host_backtrace: longshot.exe+0x1d9993d9
host_backtrace: longshot.exe+0x1d99939d
host_backtrace: longshot.exe+0x1d9a018f
host_backtrace: longshot.exe+0x1d99a0e6
host_backtrace: longshot.exe+0x1d9a069d
host_backtrace: longshot.exe+0x1d9dd34b
host_backtrace: longshot.exe+0x1d9d7640
host_backtrace: longshot.exe+0x14344e7
host_backtrace: longshot.exe+0x14343ab
host_backtrace: longshot.exe+0x13ae5397
host_backtrace: longshot.exe+0x1d99aa3a
host_backtrace: KERNEL32.dll+0x17124
host_backtrace: ntdll.dll+0x4cc91
guest_register: x0=0x1007953fa8
guest_register: x1=0x100793f6f0
guest_register: x2=0x0
guest_register: x3=0x100793f6c8
guest_register: x4=0x1007953ef0
guest_register: x5=0x0
guest_register: x6=0x1
guest_register: x7=0x0
guest_register: x8=0x100793f6f0
guest_register: x9=0x1
guest_register: x10=0x0
guest_register: x11=0xffffffff
guest_register: x12=0x0
guest_register: x13=0x1
guest_register: x14=0x1009271e76
guest_register: x15=0x10077b247f
guest_register: x16=0x63
guest_register: x17=0x0
guest_register: x18=0x0
guest_register: x19=0x100793f6c8
guest_register: x20=0x0
guest_register: x21=0x0
guest_register: x22=0x0
guest_register: x23=0x0
guest_register: x24=0x0
guest_register: x25=0x0
guest_register: x26=0x0
guest_register: x27=0x0
guest_register: x28=0x0
guest_register: x29=0x1007953fb0
guest_register: x30=0x834a3084
guest_register: x31=0x1007953fa0
guest_backtrace: 0x834a3084
guest_backtrace: 0x80df26cc
guest_backtrace: 0x834a2ec8
guest_backtrace: 0x0
dump: off
record_complete: yes

Still needed

Please add the full in-game bug report folder (especially report.txt and longshot_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.

#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.

Reported on [Discord](https://discord.com/channels/1569849200047427645/1573448048154124409/1573448048154124409) ### 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.txt` was not attached. The report provides no game log or graphics/system details. ```text Longshot crash record 1 version: v3.0.0 (source 87cb36aa) run_id: bef282d22d5553ab0f1087af85d197dd when: 20261120T205435Z uptime_s: 443 reason: unhandled exception thread: Resource Control module_offset: ucrtbase.dll+0x5b96 last_present_age_ms: unknown log: longshot_log.txt pid: 9572 started: 20261120T204712Z signal: 0 signal_code: 0 exception: 0xc00000fd fault_address_class: other host_backtrace_method: Windows unwind host_backtrace: ucrtbase.dll+0x5b96 host_backtrace: ucrtbase.dll+0x4f24 host_backtrace: ucrtbase.dll+0x4dcd host_backtrace: ucrtbase.dll+0x443d host_backtrace: ucrtbase.dll+0x112d9 host_backtrace: ucrtbase.dll+0x10d9e host_backtrace: ucrtbase.dll+0x10bfb host_backtrace: longshot.exe+0x1da9bead host_backtrace: longshot.exe+0x1d9993d9 host_backtrace: longshot.exe+0x1d99939d host_backtrace: longshot.exe+0x1d9a018f host_backtrace: longshot.exe+0x1d99a0e6 host_backtrace: longshot.exe+0x1d9a069d host_backtrace: longshot.exe+0x1d9dd34b host_backtrace: longshot.exe+0x1d9d7640 host_backtrace: longshot.exe+0x14344e7 host_backtrace: longshot.exe+0x14343ab host_backtrace: longshot.exe+0x13ae5397 host_backtrace: longshot.exe+0x1d99aa3a host_backtrace: KERNEL32.dll+0x17124 host_backtrace: ntdll.dll+0x4cc91 guest_register: x0=0x1007953fa8 guest_register: x1=0x100793f6f0 guest_register: x2=0x0 guest_register: x3=0x100793f6c8 guest_register: x4=0x1007953ef0 guest_register: x5=0x0 guest_register: x6=0x1 guest_register: x7=0x0 guest_register: x8=0x100793f6f0 guest_register: x9=0x1 guest_register: x10=0x0 guest_register: x11=0xffffffff guest_register: x12=0x0 guest_register: x13=0x1 guest_register: x14=0x1009271e76 guest_register: x15=0x10077b247f guest_register: x16=0x63 guest_register: x17=0x0 guest_register: x18=0x0 guest_register: x19=0x100793f6c8 guest_register: x20=0x0 guest_register: x21=0x0 guest_register: x22=0x0 guest_register: x23=0x0 guest_register: x24=0x0 guest_register: x25=0x0 guest_register: x26=0x0 guest_register: x27=0x0 guest_register: x28=0x0 guest_register: x29=0x1007953fb0 guest_register: x30=0x834a3084 guest_register: x31=0x1007953fa0 guest_backtrace: 0x834a3084 guest_backtrace: 0x80df26cc guest_backtrace: 0x834a2ec8 guest_backtrace: 0x0 dump: off record_complete: yes ``` ### Still needed Please add the full in-game bug report folder (especially `report.txt` and `longshot_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.
Author
Member

Files from the Discord report:

Files from the Discord report: - [crash-20261120T205456Z.txt](https://git.magicbean.dev/attachments/65d1f00d-de5d-4542-8743-31309d177e2d)
Contributor

This crash record matches the first crash in #1772. It's v3.0.0 too, has 0xc00000fd on a game thread inside ucrtbase.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:

  1. longshot_log.txt of that run. Lines like mem: commit of 0x... bytes at the commit limit made after ... or out of memory before the crash would settle it.
  2. The PC's RAM and page-file size (Settings > System > About > Advanced system settings > Performance > Advanced > Virtual memory), and the GPU.

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.

This crash record matches the first crash in #1772. It's v3.0.0 too, has `0xc00000fd` on a game thread inside `ucrtbase.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: 1. `longshot_log.txt` of that run. Lines like `mem: commit of 0x... bytes at the commit limit made after ...` or `out of memory` before the crash would settle it. 2. The PC's RAM and page-file size (Settings > System > About > Advanced system settings > Performance > Advanced > Virtual memory), and the GPU. 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.*
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot#1919
No description provided.