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
- “Label” name in Sprite Library Editor window lacks character limit causing long names go under the Object Field
- Preview image (screenshot) is not available after capturing snapshot in Memory Profiler
- Crash on UNITY_FT_Stream_ReadAt when changing TMPro properties after unloading an AssetBundle
- Particles spawn at the same position when using raw byte address buffer in VFX Graph
- Decal Shader Graph - Custom vertex interpolators are always 0
This is a duplicate of issue #897782