-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[wasm][mt] making JSImport work on worker thread #78847
Conversation
- fixed missing await on wasm instantiation - added preInitWorkerAsync - called from Module.preInit which is atually called - added preRunWorker - called after the thread is mono attached - remove forced lazy from cwraps (when called from preInit, the memory+wasm+Module is attached already)
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsThis improves initialization of the JS state on the worker thread.
Contributes to #77287
|
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/azp run runtime-wasm-non-libtests |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
This improves initialization of the JS state on the worker thread.
This is just initial work to enable JS interop.
Contributes to #77287