WebGL crashes for different users, how to analyze?

I just published a small game on Newgrounds, Kongregate, Gamejolt using the Unity WebGL export. The game runs fine for me in Google Chrome and Mozilla Firefox and even in good old Internet Explorer (without sound though.) Some players are now reporting that the game crashes for them on load or during the game. Unfortunately they mostly report it back with "Doesn't work" and a bad rating so I have little information on system configuration or what is happening during the crash. What I know is that:

• Crashes happen in Firefox as well as in Chrome
• Mostly during the loading process before the game starts

I already tried the following to fix the problems:

• Doubling the WebGL meomry size from 256 MB to 512 MB
• Removing Code Stripping form the player settings
• Disable Exceptions in the player settings

These were the measures I was able to collect from other general "WebGL crashes" threads. Do you know of any other settings that are prone to create crashes that I could try? Could you propose a methodology on how to analyze the problem without being able to reproduce the crash by myself? I'm eager to look into this and to fix this problem, but without reproducing the issue it is just wild guesses at the moment.

The game in question can be found here on Newgrounds: http://www.newgrounds.com/portal/view/666024

If you experience a crash it would be great if you could post your browser, amount of Ram on your computer, amount of ram on the browser process in the task manager (if possible) and an error message if you got any.

 

Thanks for the quick reply!

I have now published the game using the following settings:

• set WebGL Memory size 128 MB
• Strip Engine Code enabled
• Exceptions in the player settings disabled

Both Firefox and Chrome use about 600 MB of memory when running the game on my system. I will ask an user who couldn't play the game yet to try it again with these settings & I'll ask him whether it is a 32-bit browser.

 

Got a reply, the game crashes and the user has a 64 bit browser. Game also still seems to be crashing for other users as well. :-/

 

Thanks again for looking into this!

The .data file is 55 Megabytes and all .js-files together are 23 Megabytes.

 

I already tried to optimize assets before launch, since the game is also available on Android and I wanted the package to be as small as possible to save storage place on the user's devices. I have no experience with asset bundles yet, I will look into it whether I can work with them.
I already tried to reduce the Unity Heap Size to 64 MB, but this gave me an error Message during loading, if I remember correctly something along the lines that I should increase the memory amount in the player settings.

 

Nice game! However, it is too long to wait when it is loaded for the first time. Looks like you do not use the compression on the server side or the server is too slow. Hopefully, this problem will be solved with Unity 5.3.x .
Back to your question: We figured out that it is very helpful to gather the browser console log from the real players and send it to our server for analyzing the reasons why and when the game crashes.