-
Notifications
You must be signed in to change notification settings - Fork 824
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FreeBSD: wasmer hangs after running WASM file #3373
Labels
Comments
Thanks for reporting this @MalloryA. It might be something to do with our We're happy to review pull requests if someone finds a solution, but we don't currently have bandwidth to actively support BSD. |
MalloryA
added a commit
to MalloryA/wasmer
that referenced
this issue
Dec 20, 2022
This change prevents a long hang when a program exits. FreeBSD's `__deregister_frame` and `__register_frame` implementation is ported from GCC, which is why we're using the same frame registration code for FreeBSD and GNU/Linux. Link: https://github.com/freebsd/freebsd-src/blob/release/13.1.0/contrib/llvm-project/libunwind/src/UnwindLevel1-gcc-ext.c#L241-L299 Fixes: wasmerio#3373
MalloryA
added a commit
to MalloryA/wasmer
that referenced
this issue
Dec 20, 2022
This change prevents a long hang when a program exits. FreeBSD's `__deregister_frame` and `__register_frame` implementations are ported from GCC, which is why we should be using the same frame registration code for FreeBSD and GNU/Linux. Link: https://github.com/freebsd/freebsd-src/blob/release/13.1.0/contrib/llvm-project/libunwind/src/UnwindLevel1-gcc-ext.c#L241-L299 Fixes: wasmerio#3373
1 task
MalloryA
added a commit
to MalloryA/wasmer
that referenced
this issue
Dec 20, 2022
This change prevents a long hang when a program exits. FreeBSD's `__deregister_frame` and `__register_frame` implementations are ported from GCC, which is why we should be using the same frame registration code for FreeBSD and GNU/Linux. Link: https://github.com/freebsd/freebsd-src/blob/release/13.1.0/contrib/llvm-project/libunwind/src/UnwindLevel1-gcc-ext.c#L241-L299 Fixes: wasmerio#3373
MalloryA
added a commit
to MalloryA/wasmer
that referenced
this issue
Dec 20, 2022
This change prevents a long hang when a program exits. FreeBSD's `__deregister_frame` and `__register_frame` implementations are ported from GCC, which is why we should be using the same frame registration code for FreeBSD and GNU/Linux. Link: https://github.com/freebsd/freebsd-src/blob/release/13.1.0/contrib/llvm-project/libunwind/src/UnwindLevel1-gcc-ext.c#L241-L299 Fixes: wasmerio#3373
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
wasmer executes WASM files correctly, but after execution it hangs for around a minute before exiting.
Steps to reproduce
(gmake is GNU Make from package
gmake
, rust is installed via rustup and not from the FreeBSDrust
package)% gmake build-wasmer % fetch https://registry-cdn.wapm.io/contents/syrusakbary/cowsay/0.2.0/target/wasm32-wasi/release/cowsay.wasm % time ./target/release/wasmer cowsay.wasm -- hello world
Expected behavior
The cow says "hello world" and the program immediately exits. It should take a fraction of a second (and it does when I run the same command on macOS).
Actual behavior
The cow says "hello world" within a second, then the process hangs for 55 seconds. The fact that
time
reports100% cpu
is unusual too.Additional context
The text was updated successfully, but these errors were encountered: