unity 5 beta 14 webgl error

[badescuga9]

hello! i’m trying to build our project to webgl. although it works ok with unity 4.6-webplayer, when i try to compile with unity-5.0-beta14-webgl it doesn’t work.

with the non-optimised option it compiles but it crashes the chrome/firefox browser and with the optimised option i get this error:

Error building Player: Exception: Failed building WebGL Player: “C:\Program Files\Unity 5.0.0b14\Editor\Data\PlaybackEngines\webglsupport/BuildTools/Emscripten_Win/python/2.7.5.3_64bit/python.exe” “C:\Program Files\Unity 5.0.0b14\Editor\Data\PlaybackEngines\webglsupport/BuildTools/Emscripten/emcc” @“D:/Work/AoL/erpk_aol/Assets/…/Temp/emcc_arguments.resp”

before this issue i also recieve these warnings:

error;
UnityEditor.HostView:OnGUI()

WARNING root: did not see a source tree above the LLVM root directory (guessing based on directory of C:\Program Files\Unity 5.0.0b14\Editor\Data\PlaybackEngines\webglsupport/BuildTools/Emscripten_FastComp_Win\llc), could not verify version numbers match INFO root: (Emscripten: Running sanity checks) WARNING root: java does not seem to exist, required for closure compiler, which is optional (define JAVA in ~/.emscripten if you want it) warning: unresolved symbol: sem_timedwait warning: unresolved symbol: pthread_create warning: unresolved symbol: sem_post warning: unresolved symbol: _ZN4FMOD13DSPConnection6setMixEf warning: unresolved symbol: sem_wait warning: unresolved symbol: sem_destroy warning: unresolved symbol: sem_init FATAL ERROR: CALL_AND_RETRY_2 Allocation failed - process out of memory Traceback (most recent call last): File “C:\Program Files\Unity 5.0.0b14\Editor\Data\PlaybackEngines\webglsupport/BuildTools/Emscripten/emcc”, line 1452, in flush_js_optimizer_queue() File “C:\Program Files\Unity 5.0.0b14\Editor\Data\PlaybackEngines\webglsupport/BuildTools/Emscripten/emcc”, line 1364, in flush_js_optimizer_queue final = shared.Building.js_optimizer(final, js_optimizer_queue, jcache, debug_level >= 4, js_optimizer_extra_info) File “C:\Program Files\Unity 5.0.0b14\Editor\Data\PlaybackEngines\webglsupport\BuildTools\Emscripten\tools\shared.py”, line 1592, in js_optimizer return js_optimizer.run(filename, passes, listify(NODE_JS), jcache, debug, extra_info) File “C:\Program Files\Unity 5.0.0b14\Editor\Data\PlaybackEngines\webglsupport\BuildTools\Emscripten\tools\js_optimizer.py”, line 375, in run return temp_files.run_and_clean(lambda: run_on_js(filename, passes, js_engine, jcache, source_map, extra_info)) File “C:\Program Files\Unity 5.0.0b14\Editor\Data\PlaybackEngines\webglsupport\BuildTools\Emscripten\tools\tempfiles.py”, line 39, in run_and_clean return func() File “C:\Program Files\Unity 5.0.0b14\Editor\Data\PlaybackEngines\webglsupport\BuildTools\Emscripten\tools\js_optimizer.py”, line 375, in return temp_files.run_and_clean(lambda: run_on_js(filename, passes, js_engine, jcache, source_map, extra_info)) File “C:\Program Files\Unity 5.0.0b14\Editor\Data\PlaybackEngines\webglsupport\BuildTools\Emscripten\tools\js_optimizer.py”, line 285, in run_on_js filenames = pool.map(run_on_chunk, commands, chunksize=1) File “C:\Program Files\Unity 5.0.0b14\Editor\Data\PlaybackEngines\webglsupport\BuildTools\Emscripten_Win\python\2.7.5.3_64bit\lib\multiprocessing\pool.py”, line 250, in map return self.map_async(func, iterable, chunksize).get() File “C:\Program Files\Unity 5.0.0b14\Editor\Data\PlaybackEngines\webglsupport\BuildTools\Emscripten_Win\python\2.7.5.3_64bit\lib\multiprocessing\pool.py”, line 554, in get raise self._value AssertionError: Error in js optimizer:
UnityEditor.HostView:OnGUI()

standard;
UnityEditor.HostView:OnGUI()

WARNING: sanity check failed to run [Errno 13] Permission denied: ‘C:\Program Files\Unity 5.0.0b14\Editor\Data\PlaybackEngines\webglsupport/BuildTools/emscripten.config_sanity’
UnityEditor.HostView:OnGUI()

Does anyone know something about this issue?

[tomekkie2]

I am getting exactly the same.
Even on new project with one empty scene with just a camera on the build scene.

[d12frosted_1]

I am getting similar error on b17.
But it doesn’t build at all. It just crashes with this error message.

[Dustin-Horne]

Try beta 16. 14 and 15 did that for me. I haven’t tried 17 yet but 16 worked.

[jonas-echterhoff_1]

It looks like the relevant part of the error messages is:

“FATAL ERROR: CALL_AND_RETRY_2 Allocation failed - process out of memory”

It seems to run out of memory during linking. How much memory do you have? And, how much available free disk space for swap?

(That said, yes, definitely try b17!)

[d12frosted_1]

Hey, Jonas!

I have 16 GB of memory. On disk there is 250+ GB free space. I am running on OS X, Unity5b17.

[d12frosted_1]

@jonas echterhoff

It looks like the relevant part of the error messages is:

“FATAL ERROR: CALL_AND_RETRY_2 Allocation failed - process out of memory”

It seems to run out of memory during linking. How much memory do you have? And, how much available free disk space for swap?

(That said, yes, definitely try b17!)

Is it possible to increase memory allocated to emc?

[tayl0r]

bump

I’m getting the same error and I also have 16 GB memory with 200+ GB free disk space, running OSX Mavericks on a 1st generation Macbook Pro Retina and Unity 5 beta 17.

I watched the Unity process tree as it was building, and it never seems to go above 5 GB of memory used. I would assume it could grab more memory if it needed it.

OSX makes it difficult to really figure out how much true “free” memory you have left though. I’m happy to run another build running some kind of memory debug commands as the build process is running, if you can provide the command you like to get the amount of free memory.

I poked around on the emscripten site for ideas on how to decrease the memory usage, or increase the amount of memory available to emcc, and I did find 1 thing that might help: EMCC_CORES (FAQ — Emscripten 3.1.65-git (dev) documentation). Apparently, if you have a lot of cores and not so much memory, you can set that to a lower number than your real cores and it should consume less memory. Is there a way to add that to the emcc command it runs?

[jonas-echterhoff_1]

@d12frosted_1 , @tayl0r : It seems odd that you would be running out of memory on a 16GB mac. I have the same setup and I never saw that happening. Are you sure that you are seeing the same error as the thread starter? The first lines of the error are not relevant, the relevant part is “FATAL ERROR: CALL_AND_RETRY_2 Allocation failed - process out of memory”. If you are seeing that on a 16 MB mac, then either your project is somehow stretching the limits of emscripten very far, or points to a bug in emscripten. In either case, a bug report with a repro project would probably be helpful.

[tayl0r]

Yeah, it’s the same error:

FATAL ERROR: CALL_AND_RETRY_2 Allocation failed - process out of memory Traceback (most recent call last): File “/Applications/Unity5/Unity.app/Contents/PlaybackEngines/WebGLSupport/BuildTools/Emscripten/emcc”, line 1452, in flush_js_optimizer_queue() File

I submitted a bug report (# 657693) with our huge project attached. I’m pretty confident you’ll be able to reproduce it with our project. Thanks!

[jonas-echterhoff_1]

So, I looked at a bug report on this now, and discussed the behavior with Alon from mozilla (developer of emscripten). It turns out that the code had a single, very long function (several thousand lines of code), which caused the JavaScript optimizer to run out of memory when building with the “Fastest” build option (-O3 in emscripten). “Fast” (-O2 in emscripten) would work fine. Alon is working on a new version of the emscripten optimizer (which is written in C++ and not in JavaScript), which uses less memory and should fix this issue. But that is not stable yet, so until then, you can either use “Fast” to get around this, or check your project for excessively long functions and try splitting those up.

[tayl0r]

Thanks @jonas-echterhoff_1 , I will check our project for excessively long functions.