Skip to content
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

3D Mode: Invalid asm.js: Invalid member of stdlib #356

Closed
Ysurac opened this issue Oct 4, 2017 · 2 comments
Closed

3D Mode: Invalid asm.js: Invalid member of stdlib #356

Ysurac opened this issue Oct 4, 2017 · 2 comments
Assignees
Labels

Comments

@Ysurac
Copy link
Owner

Ysurac commented Oct 4, 2017

Seems to be an error seen in Chrome/Chromium 61.x
Issue open on Cesium: CesiumGS/cesium#5847

@adriweb
Copy link

adriweb commented Oct 7, 2017

FWIW, this is apparently caused by Chrome now having that chrome://flags/#enable-asm-webassembly enabled by default.

Experimental Validate Asm.js and convert to WebAssembly when valid. Mac, Windows, Linux, Chrome OS, Android
Validate Asm.js when "use asm" is present and then convert to WebAssembly. #enable-asm-webassembly

Disabling it makes the message go away. Possibly because WASM doesn't have multithreading yet (or things related to it, I haven't really checked - maybe SharedArrayBuffer or Atomics...)

I found that out here randomly trying to understand (to no avail yet) why Chrome 62 is making my multi-threaded (2 threads) emulator very slow while it's working just fine on Chrome 61 and other latest browser versions...

@Ysurac
Copy link
Owner Author

Ysurac commented Dec 11, 2017

Should be fixed since update to Cesium 1.40

@Ysurac Ysurac closed this as completed Dec 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants