The new build is able to fix the crash however breaks the functionality of the chrome flag entirely. When ran with the flag set to Auto or Wayland, Chromium will ignore this and start under XWayland the only way to actually get it launching on Wayland mode is to use the command line flag.

https://imgur.com/a/N1mx0Wg https://imgur.com/a/ZBX4TsJ

Sorry for the multiple comments however I have just stumbled across the same issue on the r/fedora subreddit as well on a Google Chrome user. The top upvoted solution was to use the "--ozone-platform=wayland" flag however this seems to be broken on the Chrome flags section causing people to have this regression.

https://www.reddit.com/r/Fedora/comments/1c7rh1k/

Looks like a black box from the recording however on the screen and on overview it's completely empty and completely glitched and breaks everything including the shell. This happens with a clean config.

https://streamable.com/kv02h7 https://imgur.com/a/4W1SP9z

That's what I'm trying to say, as soon as you set it to auto or Wayland the issue happens, however if you force X11 or keep it default the issue does not happen but it runs under Xwayland.

I have already checked the command line there were only 2 errors about the enterprise policy logger and screensaver which were also present on other Chromium versions ever since it's first install and nothing else. I also attempted to clear the GPU cache.

The issue is resolved when using Xwayland instead of native Wayland which comes at the cost of running at the wrong refresh rate (and more) in my case due to having a multiple monitor setup. I have also verified my other friend using the Electron app was running it under native Wayland.

I also asked a friend using Fedora 40 with identical GPUs (RX 7600) and he is having the same issue with an Electron app with no specific error messages.

I'd vote for rolling back as the older version has almost identical features (and even more like replay sorcery albeit on a older codebase) and had been the latest on Fedora 39 for months. The bug is pretty severe as when you hit the save button it forces the anisotropic filtering for every game (which is off by default) that MangoHud is used in and makes it miserable to debug what it's caused by.