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
-
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
- Unity overrides certain scripts even when they are named differently
- Custom Pass rendering offseted in build when modifying camera.rect
- Instanced meshes are not drawn at certain camera angles when Graphics.DrawMeshInstanced method is used
- Borders corners not properly rendered
- [WebGL] Texture is missing when Graphics.Blit() method is called for a second time in WebGL build
This is a duplicate of issue #897782