Search Issue Tracker
Fixed in 2017.1.X
Votes
1
Found in
5.6.0f1
Issue ID
892185
Regression
No
[WASM] building with full exceptions fails
-e: see title, fails with build error
--works fine with just asm.js
-repro:
--create new project
--enable WASM and full exception support
--build for WebGL
--NOTICE it fails giving the following error:
Failed running "D:\Unity Installs\5.6.0f1\Editor\Data\PlaybackEngines\WebGLSupport\BuildTools\Emscripten_Win\python\2.7.5.3_64bit\python.exe" "D:\Unity Installs\5.6.0f1\Editor\Data\PlaybackEngines\WebGLSupport\BuildTools\Emscripten\emcc" @"D:\Work\Bugs\WASM_Except\Assets\..\Temp\emcc_arguments.resp"
stdout:
stderr:WARNING:root:--separate-asm works best when compiling to HTML. otherwise, you must yourself load the '.asm.js' file that is emitted separately, and must do so before loading the main '.js` file
warning: unresolved symbol: glGetInternalformativwarning: unresolved symbol: _ZN4FMOD13DSPConnection6setMixEfwarning: unresolved symbol: glUnmapBufferwarning: unresolved symbol: glMapBufferRangewarning: unresolved symbol: glFlushMappedBufferRangeTraceback (most recent call last):
Comments (3)
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
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
TaleOf4Gamers
Jan 13, 2018 11:31
Fixed - my fault, I was using the wrong syntax. I used:
function functionName () {}
instead of the suggested:
functionName: function () {}
Lesson: actually read the docs ;)
TaleOf4Gamers
Jan 13, 2018 11:27
Im using 2017.3 just FYI
TaleOf4Gamers
Jan 13, 2018 11:27
I just got this error.