Repository navigation
WASI initialization in child thread #4102
Description
Details
wasi requires calling initialize() or start() after instantiating wasm and requires that memory is exported from wasm, but this doesn't work in multithreaded scenario (wasm32-wasi-threads target).
With wasi threads, we need to provide wasm memory created in JavaScript (new WebAssembly.Memory({ shared: true })) in main thread, and send the memory to child thread to instantiate wasm again in child thread, and it is unnecessary (and will cause error) to call initialize() or start() in child thread. So normal usage of WASI doesn't work in child thread. But we still need an "initialized" WASI instance in child thread.
Currently I'm using cloned instance object and Proxy to workaround this problem. Is there any possibility to handle this in future Node.js API change?
Node.js version
18.14.0
Example code
loadNapiModuleImpl
Operating system
macOS 13.2
Scope
code? or runtime?
Module and version
require('node:wasi').WASI
Activity
preveen-stack commentedon Aug 25, 2023
cc @nodejs/wasi
github-actions commentedon May 7, 2024
It seems there has been no activity on this issue for a while, and it is being closed in 30 days. If you believe this issue should remain open, please leave a comment.
If you need further assistance or have questions, you can also search for similar issues on Stack Overflow.
Make sure to look at the README file for the most updated links.
github-actions commentedon Jun 7, 2024
It seems there has been no activity on this issue for a while, and it is being closed. If you believe this issue should remain open, please leave a comment.
If you need further assistance or have questions, you can also search for similar issues on Stack Overflow.
Make sure to look at the README file for the most updated links.