fitzgen opened PR #14551 from fitzgen:issue-14463-host-gc-moves-object-twice to bytecodealliance:main:
We weren't zeroing out the old
VMStoreContext::last_wasm_*values when creating anEntryStoreContext, and then stack walking from a host function that wasFunc::called from another host function would see thoselast_wasm_*values both in theVMStoreContextand in the activation chain, which would lead to duplicate stack frames in the backtrace and tracing on-stack GC roots twice.Fixes #14463
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease review the Bytecode Alliance's AI tool usage policy at
https://github.com/bytecodealliance/governance/blob/main/AI_TOOL_POLICY.mdPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
fitzgen requested cfallin for a review on PR #14551.
fitzgen requested wasmtime-core-reviewers for a review on PR #14551.
:thumbs_up: alexcrichton submitted PR review.
fitzgen has enabled auto merge for PR #14551.
fitzgen added PR #14551 Fix stack walking from host functions Func::called from other host functions to the merge queue.
github-actions[bot] added the label wasmtime:api on PR #14551.
:check: fitzgen merged PR #14551.
fitzgen removed PR #14551 Fix stack walking from host functions Func::called from other host functions from the merge queue.
Last updated: Oct 11 2026 at 02:20 UTC