Skip to content

Fix dropping cached stack with Store::into_data#10009

Merged
alexcrichton merged 1 commit intobytecodealliance:mainfrom
alexcrichton:flush-on-into-inner
Jan 14, 2025
Merged

Fix dropping cached stack with Store::into_data#10009
alexcrichton merged 1 commit intobytecodealliance:mainfrom
alexcrichton:flush-on-into-inner

Conversation

@alexcrichton
Copy link
Copy Markdown
Member

@alexcrichton alexcrichton commented Jan 14, 2025

This commit fixes a regression from #9604 where using Store::into_data wouldn't properly drop a cached stack in a store like a Drop destructor. The fix here is to add the flush_fiber_stack method into the into_data here as well.

Closes #10007

This commit fixes a regression from bytecodealliance#9604 where using `Store::into_data`
wouldn't properly drop a cached stack in a store like a `Drop`
destructor. The fix here is to add the `flush_fiber_stack` method into
the `into_data` here as well.
@alexcrichton alexcrichton requested a review from a team as a code owner January 14, 2025 16:34
@alexcrichton alexcrichton requested review from fitzgen and removed request for a team January 14, 2025 16:34
@github-actions github-actions bot added the wasmtime:api Related to the API of the `wasmtime` crate itself label Jan 14, 2025
@alexcrichton alexcrichton added this pull request to the merge queue Jan 14, 2025
Merged via the queue into bytecodealliance:main with commit be40551 Jan 14, 2025
@alexcrichton alexcrichton deleted the flush-on-into-inner branch January 14, 2025 19:37
alexcrichton added a commit to alexcrichton/wasmtime that referenced this pull request Jan 14, 2025
…0009)

This commit fixes a regression from bytecodealliance#9604 where using `Store::into_data`
wouldn't properly drop a cached stack in a store like a `Drop`
destructor. The fix here is to add the `flush_fiber_stack` method into
the `into_data` here as well.
alexcrichton added a commit to alexcrichton/wasmtime that referenced this pull request Jan 14, 2025
…0009)

This commit fixes a regression from bytecodealliance#9604 where using `Store::into_data`
wouldn't properly drop a cached stack in a store like a `Drop`
destructor. The fix here is to add the `flush_fiber_stack` method into
the `into_data` here as well.
alexcrichton added a commit that referenced this pull request Jan 14, 2025
This commit fixes a regression from #9604 where using `Store::into_data`
wouldn't properly drop a cached stack in a store like a `Drop`
destructor. The fix here is to add the `flush_fiber_stack` method into
the `into_data` here as well.
alexcrichton added a commit that referenced this pull request Jan 14, 2025
This commit fixes a regression from #9604 where using `Store::into_data`
wouldn't properly drop a cached stack in a store like a `Drop`
destructor. The fix here is to add the `flush_fiber_stack` method into
the `into_data` here as well.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

wasmtime:api Related to the API of the `wasmtime` crate itself

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Calling store.into_data() after an execution triggers a debug assertion failure in drop of the pooling allocator

2 participants