We are seeing an abnormally high number of users stuck in webgl at “Downloading (0.0/1)” status in our metrics. More or less, they didnt get anywhere into the install process.
Is there any known issue that might prevent install for these users?
Thanks
No known issue. Any info about which browser/OS ? which version of Unity ?
A log from the browser would be useful too.
Lol… the title is “Chrome 42 issue” - thats the browser. OS is windows. Unity version is webgl built with 5.2.6.
The last thing in the browser log is “Downloading (0.0/1)” as far as we can tell.
Have you done any testing with ad blockers? They are becoming more common in the wild, and there are a lot of flavors out there.
“Downloading (0.0/1)” is printed by index.html . All other progress statuses are printed by UnityLoader after main game js file is loaded, processed and executed. In most cases, the problems happen there.
You can customize error handler in the Release/UnityConfig.js (generated by Unity) to see a little bit more. Add console.log before alerts. In our case, the most popular are “Out of memory…” and “Invalid array buffer length”, It is about 20% of all failed cases. 80% are peacefully dead between phases “loading” and “start to execute”.
If you can get a console log from a test case, does it produce this error?
“Uncaught RangeError: Invalid typed array length”
We are experiencing similar issues with Chrome (v46) and I believe it may have to do with errors that are not properly caught by the error handling provided by Unity (or even our own custom JS error handling). We get this specific error if we jack up the TOTAL_MEMORY value to something very large to mimick an out-of-memory error.
It seems that this error simply is not caught via window.onerror when the main js script is loaded via the .src attribute. We are looking into other ways to accommodate this.
Any thoughts?
FYI, Chrome not catching the error is due to a bug referenced here:
https://code.google.com/p/chromium/issues/detail?id=225513#c25
If the main game JS file included an onerror handler, it would be caught properly. Any way this can be part of a template or referenced externally?
For example, unity_built_game.js includes a window.onerror function that just calls UnityErrorHandler(…) which is already part of UnityConfig.js.