Search Issue Tracker
Duplicate
Votes
5
Found in
5.6.0f1
Issue ID
891835
Regression
No
[WASM] scene throws asm.setThrew
-e: so this is only half broken, the scene throws an exception in editor too but when played in with WASM throws the error reported by forum folks so this might be a first lead until we get their repro
-https://forum.unity3d.com/threads/webassembly-error-asm-setthrew.461046/
-repro:
--open attached scene
--make wasm build
--run in wasm browser
--NOTICE error being thrown
---TypeError: asm.setThrew is not a function
Comments (7)
-
twobob
Apr 18, 2017 14:20
Same. Release 5.6. f3
-
lovelle_reflexion
Apr 06, 2017 02:57
This seems to be a problem with throwing and catching in WebAssembly in general. If the build has "Explicitly Thrown Exceptions Only" enabled, it should allow throwing and catching errors, but instead at runtime it exceptions with "asm.setthrew is not a function" as soon as the exception is thrown.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture Sampling overlap causes graphical errors on specific Graphics APIs and Devices when using Framebuffer Fetch
- [Android] AssetBundle loading performance degradation when loading from a local Assetbundle
- [iOS][Android] Reflection with Generic Class returns unexpected values
- Shader Variant Collection Asset UI is hard to read when multiple Shaders and keywords are added
- Regression for "WebGL build is missing "malloc" and "free" functions when passing "-sERROR_ON_UNDEFINED_SYMBOLS=0" to emscriptenArgs"
This is a duplicate of issue #897782