WebGL build not working

Target Platforms Web
1

Hello,

I have just update one of my project and the most recent build i produce doesn’t work. I specify this because i know the build was working just before i did a small update on it. It is working locally (editor) but return error in the Chrome console on my website. Here is what the console tell me

Invoking error handler due to
Uncaught Assertion failed: klass, at: D:\APPZ\Unity 5 - free\Editor\Data\il2cpp\libil2cpp\vm\Class.cpp,1403,Init at Error
at jsStackTrace (BUILD.js:1:19540)
at stackTrace (BUILD.js:1:19711)
at ___assert_fail (BUILD.js:1:222537)
at p1m (BUILD.asm.js:18:81893)
at krn (BUILD.asm.js:18:441278)
at mrn (BUILD.asm.js:18:441933)
at qZg [Array.qZg] (BUILD.asm.js:13:322731)
at _jk [Array._jk] (BUILD.asm.js:4:11371)
at I_n [Object.I_n] (BUILD.asm.js:28:99570)
at invoke_iiii (BUILD.js:1:348665)
at L8m (BUILD.asm.js:18:197591)
at X8m (BUILD.asm.js:18:201768)
at krn (BUILD.asm.js:18:441480)
at mrn (BUILD.asm.js:18:441933)
at Jin (BUILD.asm.js:18:303575)
at D8m (BUILD.asm.js:18:194676)
at van (BUILD.asm.js:18:223867)
at mka (BUILD.asm.js:11:188271)
at ika [Object.ika] (BUILD.asm.js:11:183802)
at callMain [Object.callMain] (BUILD.js:3:30429)
at doRun (BUILD.js:3:31135)
at blob:http://www.goninteractive.com/85253312-0653-4900-9304-d4466882dfa1:3:31285

on a side note, i always get
UnityLoader.js:1 GET http://www.goninteractive.com/pathtotheproject/BUILD.mem 404 (Not Found)

but that error was there since our first build and never prevented anything to work.

I also saw on earlier build that pass a certain build size, it was taking too long for the server to decompress data resulting in error. That was with a 50mb build. I’m wondering if it is not our problem again since the datagz file take 1344ms to decompress… that’s “quite long” compare to our previous build.

anyone can help ?

2

closed the editor, reopen rebuild the exact same scene and it now work. Since uncaught assetion failed lead to a local file, what can be causing this ??? help me avoid this error as it is time consuming

3

You can enable debugging in WebGL, and even connect to it for remote debugging. You will need to do a special build with scripting enabled to be able to find the cause - up above looks like a final release build without debugging and scripts enabled.