This repository has been archived by the owner on Aug 24, 2022. It is now read-only.
Error 0xc0000409 occurs in updated crate (Win App SDK 1.1) during bootstrap if .exe does not have a manifest #43
Labels
blocked
This issue is blocked on another issue
external
This issue is a result of some external dependency
workaround-available
This issue can be worked around
Problem
I updated the project to version 1.1 of the Windows App SDK (https://github.com/kaivol/windows-app-rs/tree/was-1.1).
Running the samples without an (embedded) manifest results in a crash during the bootstrap process:
process didn't exit successfully: `target\debug\sample_xamlapp.exe` (exit code: 0xc0000409, STATUS_STACK_BUFFER_OVERRUN)
WinDbg gives the following output:
But it is not actually an
0x8007000E
E_OUTOFMEMORY
error, the actual error occurs in UndockedRegFreeWinRT/urfw.cpp:Here
CreateActCtxW
returns INVALID_HANDLE_VALUE and sets the Last-Error towhich then gets overwritten with
ERROR_OUTOFMEMORY
.I couldn't find a remark in the Windows App SDK documentation that says a manifest is required, so I'm not sure if I did an error while updating to version 1.1 or if this is a new requirement in version 1.1.
Steps to reproduce
cargo run -p sample_xamlapp
without the linewindows_app_deploy::embed_manifest();
in the associatedbuild.rs
Notes
cargo version
: cargo 1.61.0 (a028ae42f 2022-04-29)Output from
rustup show
rustup --version
: rustup 1.24.3 (ce5817a94 2021-05-31)cmd /c ver
: Microsoft Windows [Version 10.0.22621.1]Output from
get-appxpackage *winappruntime*
The text was updated successfully, but these errors were encountered: