Chrome crashes even with empty project ('Aw, Snap!')

Unity Engine
,
1

We are having issues with Chrome crashing unity WebGL builds even with a completely new/empty project. It seems to happen at the end of loading Unity. (Unity 2018.2.17f1)

It doesn’t happen every time but if you refresh it like 10 times in a row then it crashes at least once.

We’ve been trying to debug it but the profiler wont connect to it because the engine hasn’t started running yet. Here is the message we get:

Is anybody else getting this. (it happens running from an online server and also when run on a local webserver such as WAMP.

4392406--399238--Aw Snap.PNG
4392406--399238--Aw Snap.PNG1917×1006 14.3 KB

2

Increase the initial memory size in the player settings to 512 and test it again.

1 Like
3

Thanks, I did that and it still was happening :frowning:

One of the devs on our team actually worked it out this morning. It only happens if you have the chrome dev tools open while loading the page. If you do not have dev tools inspector open then it doesn’t crash.

I guess it must be an issue with how unity writes stuff out to the console, or perhaps an issue with the dev tools profiling the memory or something?

4

@robrab2000-aa follow this thread and the linked post there.