You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue can be reproduced in a C program that invokes wasm_engine_new,
forks itself and then proceed to invoke the remaining C API calls in the child
process.
The engine created in the main process doesn't even need to be used
in the child process to trigger the segmentation fault.
The following C code, adapted from ./examples/hello.c, triggers the behaviour:
Test Case
Although the behaviour observed and here described does not seem dependent on the Wasm file itself at all, this is the one considered for tests:
Steps to Reproduce
This issue can be reproduced in a C program that invokes
wasm_engine_new
,forks itself and then proceed to invoke the remaining C API calls in the child
process.
The engine created in the main process doesn't even need to be used
in the child process to trigger the segmentation fault.
The following C code, adapted from
./examples/hello.c
, triggers the behaviour:Expected Results
I expect to have something like this from the standard output:
Actual Results
Versions and Environment
Wasmtime version or commit: v8.0.1
Operating system: macOS
Architecture: x86, arm64
Extra Info
Although this behaviour can be consistently observed, it doesn't always happen.
It also seems to be more easily observed in arm64 than in x86.
The text was updated successfully, but these errors were encountered: