You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
When wasmtime handles a call to host functions it uses a mutable pointer to the contents of FunctionExecutorState and linear memory. The problem arises when using the sandbox wasmtime reenters into the host handling routines and obtains the mutable reference to the same items again.
The text was updated successfully, but these errors were encountered:
I think this is not relevant: The issue is still present even though we that wasmi is being used for sandbox. It just the implementation of the wasmtime executor backend spawns this issue.
When wasmtime handles a call to host functions it uses a mutable pointer to the contents of
FunctionExecutorState
and linear memory. The problem arises when using the sandbox wasmtime reenters into the host handling routines and obtains the mutable reference to the same items again.The text was updated successfully, but these errors were encountered: