Skip to content
This repository has been archived by the owner on Sep 19, 2022. It is now read-only.

Wasm Compability Issue #10

Closed
AnneKitsune opened this issue Jul 26, 2020 · 2 comments
Closed

Wasm Compability Issue #10

AnneKitsune opened this issue Jul 26, 2020 · 2 comments

Comments

@AnneKitsune
Copy link
Contributor

AnneKitsune commented Jul 26, 2020

Here is what I posted on the rust discord server. Still waiting for a reply.

I have some issues getting SharedArrayBuffer to work properly on newer firefox versions.

I did the changes required from https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/SharedArrayBuffer/Planned_changes but had no success in using post_message in a web worker.

I did verify that both headers are set and that the window is in a secure context. The SharedArrayBuffer does work, but when using post_message from the web worker, I get a panic.

My project uses the web_worker crate, which is itself based on the wasm_bindgen/examples/raytrace_parallel.
This example is also broken.

Anyone knows who is the current maintainer of the wasm_bindgen examples?

@erlend-sh
Copy link
Contributor

We’ve got a working web version now: https://shotcaller.jojolepro.com/

Can this be considered resolved? Is our workaround documented?

@AnneKitsune
Copy link
Contributor Author

The workaround we used is that we created a single-threaded specs dispatcher. This way, we don't need to get threads to work with wasm at all. Bracket was really helpful with this :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants