Skip to content

Windows app: raea-page-host.exe crashes with a main-thread stack overflow (1 MB stack, 0xc000041d) #112

Open

Description

@augusbazan

Summary

On Windows, the desktop app (raea-0.1.1-windows-x86_64.app.exe, installed per-user via NSIS) opens, runs slowly, then the window closes by itself. raea-page-host.exe crashes with a stack overflow on its main thread.

Evidence

app.log.window.err ends with:

raea-page: a frame's script /artifact.js isn't a file inside the page's root
WARN symphonia_format_isomp4::atoms::stbl: ignoring stss atom.

thread 'main' (34408) has overflowed its stack

Windows Application log (Event ID 1000 / WER 1001), identical on 3 launches:

Faulting application: raea-page-host.exe 0.0.0.0
Exception code: 0xc000041d   (STATUS_FATAL_USER_CALLBACK_EXCEPTION)
Fault offset:   0x000000000a2e9817

Same code and same offset every time, so it is deterministic.

Likely cause

The PE header of raea-page-host.exe reserves a 1 MB stack (SizeOfStackReserve = 1,048,576), the Windows default. For comparison, in the same release:

binary SizeOfStackReserve
raea.exe 8 MB
raea-page-host.exe 1 MB
raea-rune-host.exe 1 MB
raea-perceive.exe 1 MB

So the CLI got a bigger main-thread stack but the window host did not. The overflow comes right after an MP4 is opened (the symphonia warning), inside a window callback, which would explain 0xc000041d. I have not confirmed which call chain overflows; that is a hypothesis from the log order.

Possible fix: link raea-page-host (and probably raea-rune-host) with /STACK:8388608 (e.g. -C link-arg=/STACK:8388608 in .cargo/config.toml for the x86_64-pc-windows-msvc target), or run the page host's main loop on a thread spawned with an explicit stack size.

Slowness

Not diagnosed. Possibly related to the hardware below, possibly to the same startup path. Noting it in case it helps.

Environment

  • raea 0.1.1 (Windows x86_64 release, app installer + CLI zip; SHA256 of both matched the .sha256 files)
  • Windows 11 Home 10.0.26200
  • AMD Radeon Graphics (integrated, device 0x1681), driver 32.0.21045.16010, 15 GB RAM
  • Launched from the Start Menu shortcut (launch.ps1)

Repro

  1. Install raea-0.1.1-windows-x86_64.app.exe (/S or interactive).
  2. Launch "raea" from the Start Menu.
  3. The window opens, is slow, and closes within seconds; raea-page-host.exe is gone and WER logs the crash above.

The CLI (raea render) works fine on the same machine.

Activity

  1. shinyobjectz commented on Nov 12, 2026

    @shinyobjectz
    Owner

    Thank you: the PE header table made this a one-line diagnosis. You had it right. engine/cli/build.rs gave raea.exe an 8 MB main-thread stack and nothing else got one, so the app's window process ran on Windows' 1 MB default and overflowed it inside a window callback as soon as the MP4 opened.

    Fixed on main in d70c8e6: .cargo/config.toml now links every Windows MSVC executable with /STACK:8388608, so raea-page-host, raea-rune-host and raea-perceive match raea.exe. No published Windows build has it yet; it'll be in the next one, and I'll post here when there's a build you can try. The slowness you noted is separate (the integrated Radeon, most likely #66's family); if it's still slow once the crash is gone, a fresh issue with what the window is doing while it's slow would help.

  2. added
    needs confirmingFixed in a build; waiting for the reporter to confirm it on their machine
    on Nov 12, 2026
  3. shinyobjectz commented on Nov 12, 2026

    @shinyobjectz
    Owner

    There's now a build with the fix: v0.1.2-rc3, a pre-release. raea-0.1.2-rc3-windows-x86_64.zip has raea-page-host.exe linked with the 8 MB stack (d70c8e6). When you have a moment, could you open the same MP4 in the app from that zip and tell me whether the window stays up? If it still crashes, the exit code and dumpbin /headers raea-page-host.exe | findstr stack would tell me whether the new stack size made it into the build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs confirmingFixed in a build; waiting for the reporter to confirm it on their machine

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions