assertion failed: self.stacks.is_empty() · wasmtime

Stream: wasmtime

Topic: assertion failed: self.stacks.is_empty()

Tomas Olvecky (Jan 13 2025 at 19:27):

After updating to wasmtime 28 I see a panic with the message above when shutting down wasmtime: pooling.rs#L319
Is there a cleanup I have to perform when using the pooling allocator?

wasmtime/crates/wasmtime/src/runtime/vm/instance/allocator/pooling.rs at release-28.0.0 · bytecodealliance/wasmtime

A lightweight WebAssembly runtime that is fast, secure, and standards-compliant - bytecodealliance/wasmtime

Alex Crichton (Jan 13 2025 at 19:30):

Hm that may indicate a bug because nothing about that should have changed. You're not mem::forget-ing anything are you?

Tomas Olvecky (Jan 13 2025 at 20:25):

Nope. If I start the server and perform the graceful shutdown without running any executions, the panic won't appear.

Alex Crichton (Jan 13 2025 at 20:43):

Hm ok, how easy would it be to either reduce this to something you can share or share reproduction steps?

Tomas Olvecky (Jan 14 2025 at 11:23):

I've managed to reproduce the issue in the wasmtime repo, created an issue for it here

Calling `store.into_data()` after an execution triggers a debug assertion failure in `drop` of the pooling allocator · Issue #10007 · bytecodealliance/wasmtime

Calling store.into_data() after an execution finishes will trigger a panic in this debug assertion of the pooling allocator's drop method. Test Case This commit will trigger the bug in a test: toma...

Alex Crichton (Jan 14 2025 at 15:32):

thanks!

Last updated: Jan 24 2025 at 00:11 UTC