-
Notifications
You must be signed in to change notification settings - Fork 5.4k
Closed
Labels
arch-wasmWebAssembly architectureWebAssembly architecturearea-VM-meta-monoos-wasiRelated to WASI variant of arch-wasmRelated to WASI variant of arch-wasmtest-failure
Milestone
Description
[23:40:07] info: Failed to load ./icudt.dat
[23:40:07] info: Process wasmtime.exe exited with 3
[23:40:07] info: Error: failed to run main module `dotnet.wasm`
[23:40:07] info: Waiting to flush log messages with a timeout of 120 secs ..
[23:40:07] info:
[23:40:07] info: Caused by:
[23:40:07] info: 0: failed to invoke command default
[23:40:07] info: 1: error while executing at wasm backtrace:
[23:40:07] info: 0: 0x26594e - <unknown>!fseek
[23:40:07] info: 1: 0x5b12 - <unknown>!load_icu_data
[23:40:07] info: 2: 0x5bd8 - <unknown>!mono_wasm_load_runtime
[23:40:07] info: 3: 0x60be - <unknown>!main
[23:40:07] info: 4: 0x262ec3 - <unknown>!__main_void
[23:40:07] info: 5: 0x58ee - <unknown>!_start
[23:40:07] info: 6: 0x276152 - <unknown>!_start.command_export
[23:40:07] info: note: using the `WASMTIME_BACKTRACE_DETAILS=1` environment variable may show more debugging information
[23:40:07] info: 2: wasm trap: uninitialized element
[23:40:07] fail: Application has finished with exit code 3 but 0 was expected
cc @ilonatommy
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
arch-wasmWebAssembly architectureWebAssembly architecturearea-VM-meta-monoos-wasiRelated to WASI variant of arch-wasmRelated to WASI variant of arch-wasmtest-failure