All Godot 3.5 exports crash on Chrome for Android?

Netaction

Hi!

Dumb issue, but I am trying to fix it for 10 hours now.
My game crashes on Chrome for Android. I tested 3 different smartphones. The loading bar moves a bit and then the whole tab stops, showing Chrome's Oups message.
https://www.ventusmaris.de/mittelalter/

I took a new Windows 11 PC, installed a fresh Godot 3.5.3, added the latest HTML5 exporter and created a minimal scene with just one image. It crashes.
Then I connected the Chrome Developer Console via USB to see console errors. This made the game work. I found other Webassembly projects with the same issue. They crash on Chrome for Android but don't crash if DevTools are enabled.

My previously working games stopped working so I assume Chrome changed, not Godot.

I installed the game on completely different web servers on different hosters, same issues everywhere.

As this is 100% reproducable with different phones and different exporting computers, does anyone else have this issue?

Cheers
Thomas

DaveTheCoder

I can run the app in the Chrome browser on my Android phone. I tried a couple of the menu buttons, and they worked. The phone is a Galaxy S9, running Android 10 and Chrome 117.0.5938.60.

Netaction but don't crash if DevTools are enabled.

I have Developer Mode enabled on the phone, if that's what you mean.

Netaction

DaveTheCoder I have Developer Mode enabled

Thank you for the test. The Developer Mode does not fix the issues of my phone but actually connecting it via USB to a computer running Chrome to inspect the DOM and console.

I have the exact same Chrome version on different devices. Some show the "Aw Snap" page of a crashed tab without any interaction and some don't.

On Browserstack all phones work. But they all export their console so maybe this is the reason why they work.

Other Godot Games also crash my phone and some phones of my collegues. I think they worked two months ago. https://trhrichard.itch.io/minecraft-2d

Netaction

I finally found the issue on Github so the discussion will continue there.

https://github.com/godotengine/godot/issues/82015

ahmad3470

Hi Thomas,

You're not alone on this—others have run into the same issue recently. It’s most likely caused by a recent Chrome for Android update that changed how it handles WebAssembly or memory allocation. Since your project runs fine when DevTools are open, that usually points to a timing or threading issue that DevTools unintentionally “fixes.” One thing to try is lowering the memory setting in your HTML5 export template. Go into your export settings and reduce the heap_size in the HTML shell file, maybe start with 32MB or 64MB and test from there.

Also, try switching the thread_model to "single-threaded" in the export settings. Godot’s multithreading on the web can be unstable on some mobile browsers, and recent browser updates might have broken compatibility further. Until there's a fix from the Godot or Chromium teams, going single-threaded can help things stay stable on mobile. Keep an eye on GitHub issues for both Godot and https://minecrraftapk.com/ —others are flagging this too.

Regards