Search Issue Tracker

Fixed in 2018.2.X

Votes

0

Found in

2018.1.0f2

Issue ID

1032960

Regression

No

[WebGL] Web Assembly build fails with error when Exceptions are enabled

WebGL

-

Steps to reproduce:
1. Open user-submitted project "ProjectQuestIon.zip"
2. Build for WebGL (make sure Linker Target is WebAssembly and Enable Exceptions is set to Full With Stacktrace)

Expected result: build does not fail
Actual result: build fails with the following error:

Failed running "X:\PATH_TO_UNITY\Editor\Data\PlaybackEngines\WebGLSupport\BuildTools\Emscripten_Win\python\2.7.5.3_64bit\python.exe" "X:\PATH_TO_UNITY\Editor\Data\PlaybackEngines\WebGLSupport\BuildTools\Emscripten\emcc" @ "X:\PATH_TO_ATTACHED_PROJECT\case_1032960-ProjectQuestIon\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` filewarning: unresolved symbol: openWindowTraceback (most recent call last): File "C:\Program Files\2018.1\2018.1.0f2_d4d99f31acba\Editor\Data\PlaybackEngines\WebGLSupport\BuildTools\Emscripten\emcc", line 13, in <module> emcc.run() File "C:\Program Files\2018.1\2018.1.0f2_d4d99f31acba\Editor\Data\PlaybackEngines\WebGLSupport\BuildTools\Emscripten\emcc.py", line 2145, in run subprocess.check_call(cmd) File "C:\Program Files\2018.1\2018.1.0f2_d4d99f31acba\Editor\Data\PlaybackEngines\WebGLSupport\BuildTools\Emscripten_Win\python\2.7.5.3_64bit\lib\subprocess.py", line 542, in check_call raise CalledProcessError(retcode, cmd)subprocess.CalledProcessError: Command '[u'C:\\Program Files\\2018.1\\2018.1.0f2_d4d99f31acba\\Editor\\Data\\PlaybackEngines\\WebGLSupport\\BuildTools\\Emscripten_FastComp_Win\\binaryen\\bin\\asm2wasm', 'C:\\Users\\default.DESKTOP-AEA1AI9\\Desktop\\Week 19\\case_1032960-ProjectQuestIon\\Temp\\StagingArea\\Data\\linkresult_wasm\\build.asm.js', '--total-memory=536870912', '-O3', '--mem-init=C:\\Users\\default.DESKTOP-AEA1AI9\\Desktop\\Week 19\\case_1032960-ProjectQuestIon\\Temp\\StagingArea\\Data\\linkresult_wasm\\build.js.mem', '--mem-base=1024', '--wasm-only', '--symbolmap=C:\\Users\\default.DESKTOP-AEA1AI9\\Desktop\\Week 19\\case_1032960-ProjectQuestIon\\Temp\\StagingArea\\Data\\linkresult_wasm\\build.js.symbols', '-o', 'C:\\Users\\default.DESKTOP-AEA1AI9\\Desktop\\Week 19\\case_1032960-ProjectQuestIon\\Temp\\StagingArea\\Data\\linkresult_wasm\\build.wasm']' returned non-zero exit status -1073741571
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

Reproduced with: 2017.2.0f3, 2017.3.1f1, 2017.4.4f1, 2018.1.0f2, 2018.2.0b6
Not reproduced with: 2018.2.X
Log in to vote on this issue

Comments (8)

  1. ahmedaniss

    Jun 14, 2020 04:43

    i fix this problem here https://youtu.be/uRxjC-d1b0g

  2. ahmedaniss

    Dec 02, 2019 22:38

    i fix this problem here : https://www.youtube.com/watch?v=_Jl0q5U3R1A you can follow my step to fix this problem .

  3. unity_3jbc22

    Jul 23, 2019 21:33

    I got this error in 2019.1.0f2

  4. Darth-Zoddo

    Jan 31, 2019 07:49

    Reproduced in 2018.2.9f1

  5. blue-mile

    Aug 07, 2018 05:04

    I'm having the same problem in 2018.2.2f1

  6. guydunkski

    Jul 09, 2018 12:44

    I must joib ROYVANEIJNDHOVEN question, this is quite critical if your target platform is WebGL and on the LTS version those kind of bugs should be fixed. Quite hard to debug Webgl without the stack trace!

  7. Roywise

    Jul 05, 2018 13:29

    Will this fix be backported to 2017.4 LTS? The description does not say.

  8. Mindslicer

    Jun 20, 2018 07:22

    Got same error

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues