RESOLVED DUPLICATE of bug 247327 247860
REGRESSION (Safari 16.1): All Godot Engine Web Exports fail to load
https://bugs.webkit.org/show_bug.cgi?id=247860
Summary REGRESSION (Safari 16.1): All Godot Engine Web Exports fail to load
dnxgr623
Reported 2022-11-13 08:21:40 PST
Created attachment 463506 [details] Gnome Web Console Log Since Safari 16.1, every web game created by the Godot Engine crashes on loading. This did not happened with Safari 16.0 and previous versions. It happens even when exporting a completely empty, default project. It also happens with Gnome Web 42.4 "Powered by WebKitGTK 2.36.8", I don't know where the regression started here. The console with Safari only has those 2 entries: Godot Engine v3.5.1.stable.official.6fed1ffa3 - https://godotengine.org OpenGL ES 2.0 Renderer: WebKit WebGL Gnome Web gives a few more entries, I attached the log. Bug report on Godots Bugtracker: https://github.com/godotengine/godot/issues/67949 I tested it on an Intel Mac running MacOS Monterey and Safari 16.1 and Ubuntu Linux running Gnome Web 42.4, it was confirmed to happen on other platforms by other Godot users.
Attachments
Gnome Web Console Log (2.31 KB, text/plain)
2022-11-13 08:21 PST, dnxgr623
no flags
Crash log from console.app (28.47 KB, text/plain)
2022-12-14 10:31 PST, dnxgr623
no flags
Alexey Proskuryakov
Comment 1 2022-11-14 17:50:53 PST
Sounds like there is no OS level crash, so re-titling. Could you please provide steps to reproduce, such as a link to follow? This is clearly an important issue, but even so, figuring out how to create a project may turn out to be infeasible with the volume of bugs that we analyze.
Radar WebKit Bug Importer
Comment 2 2022-11-14 17:51:03 PST
dnxgr623
Comment 3 2022-11-15 05:21:07 PST
This is an empty default project exported with the current Godot 3.5.1: https://www.threetrees.eu/EmptyGodotExport/index.html
Alexey Proskuryakov
Comment 4 2022-11-15 08:42:22 PST
This page loads to a grey screen in Safari 16.2 in macOS Ventura 13.1 beta on M1 Mac, same as Chrome. Same on a newer Safari build on Intel. Is this the expected behavior? I do see that it's reported against Safari on macOS Monterey, which I didn't test.
dnxgr623
Comment 5 2022-11-15 08:48:10 PST
Grey screen is intended. On Safari 16.1 (Intel, macOS 12.6.1), it does not load but fails constantly. So either this is fixed in 16.2, or it only happens on Monterey.
Alexey Proskuryakov
Comment 6 2022-11-15 09:02:20 PST
Getting a grey screen in Safari 16.1 running on macOS Monterey 12.5.1 (21G83) too, on an iMac Pro. What hardware are you seeing this with?
dnxgr623
Comment 7 2022-11-15 11:26:19 PST
Macbook Pro early 2015 On Godot discord this was confirmed by someone with a 2017 Macbook.
dnxgr623
Comment 8 2022-11-15 11:29:26 PST
Could you also please try an actual game in 16.1/16.2 on your machine, for example: https://philterphil.itch.io/dont-enter-the-forest
Rémi Verschelde
Comment 9 2022-11-16 07:12:14 PST
I've uploaded two versions of the open source Godot game Jetpaca (https://github.com/KOBUGE-Games/jetpaca) with Godot 3.5.1 which can (probably, I have no Apple device to test Safari) be used to reproduce this issue. - WebGL 1.0: https://akien.itch.io/jetpaca - WebGL 2.0: https://akien.itch.io/jetpaca-webgl2 Note the download is ~50 MB for each (or maybe less if itch.io compressed it). It's a debug export (albeit without debug symbols), with verbose output (which triggers some OpenGL debugging logic) so there might be more WebGL debugging info than in release uploads. You can also recreate this upload locally (for Jetpaca or for any Godot project, including a brand new one with just a hello world) with the following steps: - Download Godot 3.5.1: https://godotengine.org/download/ - Clone https://github.com/KOBUGE-Games/jetpaca and import it in Godot's project manager (or create a new GLES2 (WebGL 1) or GLES3 (WebGL 2) project and make a simple scene) - Install export templates with Editor > Manage Export Templates - Add export preset for HTML5 with Project > Export > Add... > HTML5 - This should add a HTML5 logo in the top right corner of the editor which can be used for one-click deploy. Click it and Godot should host a local HTTPS server with the appropriate headers, so you can run the project on localhost:8060 in any browser.
Alexey Proskuryakov
Comment 10 2022-11-16 09:03:36 PST
Please note that there is another issue tracking issues with Godot, bug 237658. It seems like it's somewhat different, so we should keep this bug focused on exactly the issue reported originally, not conflating it with the other one.
dnxgr623
Comment 11 2022-11-24 16:02:59 PST
I hope this helps: I asked everyone I know with a Mac to try. It looks like it depends on the device if it will load or not - everything 2020 (possible 2019, one device worked) and newer seems to work without issues, while 2015 and older devices (up to 2013, seems to be the olders 16.1 runs on) will not load Godot exports. So might be something GPU driver related? Did not collected enough data for devices inbetween 2015 and 2020 unfortunatelly.
Dan Glastonbury
Comment 12 2022-12-11 14:53:07 PST
When the page crashes in Safari 16.1, is there an associated crash in console.app > Crash Reports > com.apple.WebKit.WebContent?
dnxgr623
Comment 13 2022-12-14 10:31:16 PST
Created attachment 464047 [details] Crash log from console.app
dnxgr623
Comment 14 2022-12-14 10:32:03 PST
Added the crash log from console.app I just upgraded to Safari 16.2 and the crash persists.
Dean Jackson
Comment 15 2022-12-21 12:38:42 PST
This was fixed here: Committed 256539@main (829dab614cc1): <https://commits.webkit.org/256539@main> *** This bug has been marked as a duplicate of bug 247327 ***
Dean Jackson
Comment 16 2022-12-21 12:39:09 PST
I'm not sure when it will get into a Safari update though, sorry. ASAP.
dnxgr623
Comment 17 2023-01-25 05:08:44 PST
I don't know if the supposed fix made it into Safari 16.3, but in the case it did I wanted to leave the information here that the bug is still present.
dnxgr623
Comment 18 2023-03-27 14:08:55 PDT
Last update: Safari 16.4 fixed the issue!
Note You need to log in before you can comment on or make changes to this bug.