-
Notifications
You must be signed in to change notification settings - Fork 452
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
CompileError: AsyncCompile: Wasm decoding failed: expected magic word 00 61 73 6d, found 3c 21 44 4f @+0] #1031
Comments
Those bytes are "<!DO" in ASCII, so probably you are trying to load an HTML document. Anyway, this repo is for the Wasm spec and related issues. I suggest asking your question (with a bit more context) on StackOverflow. |
@rossberg can you please elaborate upon this?
|
The bytes 3c 21 44 4f are the string "<!DO". The error message says that they occur in place of the Wasm "magic word", which should be the first 4 bytes of a valid Wasm module. |
Any possible solution to it? Thanks a ton!! |
What's most likely happening is that when you try to load the So make sure that your server is configured correctly, that the If you're still running into problems, you should ask on StackOverflow, not here. |
Thanks @Pauan , this is something I can proceed with. |
Check your webserver's redirect filter... That worked for me |
Uncaught (in promise) RuntimeError: Aborted(CompileError: WebAssembly.instantiate(): expected magic word 00 61 73 6d, found 3c 21 44 4f @+0) getting this error. It shows that .wasm file is loaded as a html file. If any can help me with the same to know ho to use wasm with nodejs project. |
I am running my unit tests with tape in which the test is running after browserified. Now when I try running the tests which include my wasm code compiled with web assembly explorer, it shows me this error.
The file is a wasm file and not a wat file.
Please help me with this.
Also noting that the code works in chrome.
The text was updated successfully, but these errors were encountered: