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
is_web_worker_thread will evaluate to true, which will post a message to the parent page which has no handler for it.
spawn_for_context must be called at least once regardless of whether it is a worker or the browser main thread. This can possibly be addressed by adding a global and changing it to this:
I've encountered an unexpected deadlock when using
wasm_thread
in a binary running directly in a dedicated web worker.It can be reproduced reliably as demonstrated here.
After some digging I believe the deadlock stems from here
wasm_thread/src/wasm32/mod.rs
Lines 254 to 258 in 7ec4868
is_web_worker_thread
will evaluate totrue
, which will post a message to the parent page which has no handler for it.spawn_for_context
must be called at least once regardless of whether it is a worker or the browser main thread. This can possibly be addressed by adding a global and changing it to this:The text was updated successfully, but these errors were encountered: