wasmtime / issue #4912 `qemu-riscv64` will exhaust all p... · git-wasmtime

Stream: git-wasmtime

Topic: wasmtime / issue #4912 `qemu-riscv64` will exhaust all p...

Wasmtime GitHub notifications bot (Sep 15 2022 at 08:04):

yuyang-ok edited issue #4912:

Finished test [unoptimized + debuginfo] target(s) in 26.99s
Running /home/yuyang/projects/qemu/build/qemu-riscv64 -L /usr/riscv64-linux-gnu -E LD_LIBRARY_PATH=/usr/riscv64-linux-gnu/lib -E WASMTIME_TEST_NO_HOG_MEMORY=1 /home/yuyang/projects/wasmtime/target/riscv64gc-unknown-linux-gnu/debug/deps/host_segfault-0362e2365a90b3f7
thread 'main' panicked at '

expected a stack overflow on hit async stack guard page with pooling allocator
got status: signal: 9 (SIGKILL)

', tests/host_segfault.rs:213:13
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
error: test failed, to rerun pass '--test host_segfault'

Wasmtime GitHub notifications bot (Sep 15 2022 at 08:07):

yuyang-ok edited a comment on issue #4912:

https://github.com/bytecodealliance/wasmtime/blob/main/crates/runtime/src/instance/allocator/pooling.rs#L718

Wasmtime GitHub notifications bot (Sep 15 2022 at 08:08):

yuyang-ok deleted a comment on issue #4912:

https://github.com/bytecodealliance/wasmtime/blob/main/crates/runtime/src/instance/allocator/pooling.rs#L718

Wasmtime GitHub notifications bot (Sep 15 2022 at 08:09):

yuyang-ok commented on issue #4912:

@jameysharp look like the env var WASMTIME_TEST_NO_HOG_MEMORY not used no test host_segfault.

Wasmtime GitHub notifications bot (Sep 15 2022 at 09:11):

yuyang-ok commented on issue #4912:

https://github.com/bytecodealliance/rustix/issues/400

Wasmtime GitHub notifications bot (Sep 16 2022 at 01:38):

yuyang-ok commented on issue #4912:

(https://github.com/bytecodealliance/wasmtime/blob/main/crates/runtime/src/instance/allocator/pooling.rs#L718)
MemoryPool is trying to alloc very huge area (6002G) in virutal address space.
maybe this is a little incompatible with qemu-riscv64.

Wasmtime GitHub notifications bot (Sep 16 2022 at 01:56):

yuyang-ok edited a comment on issue #4912:

(https://github.com/bytecodealliance/wasmtime/blob/main/crates/runtime/src/instance/allocator/pooling.rs#L718)
MemoryPool is trying to alloc very huge area (6002G) in virtual address space.
maybe this is a little incompatible with qemu-riscv64.

Wasmtime GitHub notifications bot (Sep 16 2022 at 05:09):

yuyang-ok commented on issue #4912:

https://gitlab.com/qemu-project/qemu/-/issues/1214

Wasmtime GitHub notifications bot (Sep 16 2022 at 05:09):

yuyang-ok closed issue #4912:

expected a stack overflow on hit async stack guard page with pooling allocator
got status: signal: 9 (SIGKILL)

', tests/host_segfault.rs:213:13
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
error: test failed, to rerun pass '--test host_segfault'

Wasmtime GitHub notifications bot (Sep 16 2022 at 05:09):

yuyang-ok deleted a comment on issue #4912:

https://github.com/bytecodealliance/rustix/issues/400

Wasmtime GitHub notifications bot (Sep 16 2022 at 05:09):

yuyang-ok commented on issue #4912:

https://gitlab.com/qemu-project/qemu/-/issues/1214

Wasmtime GitHub notifications bot (Sep 16 2022 at 05:09):

yuyang-ok closed issue #4912:

expected a stack overflow on hit async stack guard page with pooling allocator
got status: signal: 9 (SIGKILL)

', tests/host_segfault.rs:213:13
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
error: test failed, to rerun pass '--test host_segfault'

Wasmtime GitHub notifications bot (Sep 16 2022 at 05:31):

yuyang-ok deleted a comment on issue #4912:

https://gitlab.com/qemu-project/qemu/-/issues/1214

Last updated: Oct 23 2024 at 20:03 UTC