dicej opened PR #11655 from dicej:sync-lower-subtask-lifecycle to bytecodealliance:main:
Previously, we were unconditionally deleting the callee subtask once it returned a value to a sync-lowered call, but that's only appropriate if the subtask has exited. Otherwise, it needs to keep running and only be deleted once it actually exits.
Thanks to Luke for the
sync-streams.wasttest that uncovered this, which I've copied from thecomponent-modelrepo.This also makes a couple of debug logging tweaks that proved useful while investigating the above issue.
<!--
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 ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
dicej requested wasmtime-core-reviewers for a review on PR #11655.
dicej requested alexcrichton for a review on PR #11655.
dicej updated PR #11655.
alexcrichton submitted PR review.
alexcrichton has enabled auto merge for PR #11655.
alexcrichton edited PR #11655:
Previously, we were unconditionally deleting the callee subtask once it returned a value to a sync-lowered call, but that's only appropriate if the subtask has exited. Otherwise, it needs to keep running and only be deleted once it actually exits.
Thanks to Luke for the
sync-streams.wasttest that uncovered this, which I've copied from thecomponent-modelrepo.This also makes a couple of debug logging tweaks that proved useful while investigating the above issue.
Closes #11611
<!--
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 ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
alexcrichton merged PR #11655.
Last updated: Dec 06 2025 at 06:05 UTC