Brave beta (and nightly) fullscreen YouTube crash in Wayland

Description of the issue:

Brave Beta Version 1.52.108 Chromium: 114.0.5735.26 (Official Build) beta (64-bit)
and Nightly Version 1.53.60 Chromium: 114.0.5735.26 (Official Build) nightly (64-bit) both crash when attempting to fullscreen a YouTube video while the “Preferred Ozone Platform” flag is set to “Wayland”.

How can this issue be reproduced?

  1. Install either a nightly or beta build of Brave. In my case I tested with both brave-beta-bin and brave-nightly-bin on Arch from the AUR.
  2. Navigate to brave://flags and set the “Preferred Ozone Platform” to “Wayland”.
  3. Go to and try to watch any video in fullscreen.

Expected result:

I should be able to use Brave in Wayland mode without crashing while attempting to watch fullscreen YouTube videos.

Brave Version( check About Brave):

  • Version 1.52.108 Chromium: 114.0.5735.26 (Official Build) beta (64-bit) and
  • Version 1.53.60 Chromium: 114.0.5735.26 (Official Build) nightly (64-bit)

Additional Information:

I uploaded crash logs for this issue as Crash ID: crash/59f20800-8e2d-1b0a-0000-000000000000 and also reported this issue on GitHub.

This issue is not present in the stable Brave release Version 1.51.118 Chromium: 113.0.5672.126 (Official Build) (64-bit). This issue is also not present when running either Brave Beta or Nightly under XWayland by not setting the “Preferred Ozone Platform” flag.

My system is running Arch Linux 6.3.3-arch1-1 using Wayland with the Hyprland window manager on Intel and NVIDIA hardware. I am happy to provide additional details as needed to help debug. For some reason the bug reporting site won’t let me use the linux tag in the beta builds forum.

@TimTinkers it helps if you can share links to Github when you create an issue.

I also want to ask, I see you mentioned Beta and Nightly. Have you tested on Release version? Just wanting to confirm if you can replicate there or if it is indeed something changing in code?

Here is a link to the corresponding GitHub issue. I did mention in the original post but didn’t surface it prominently: this issue is not present in the stable build on the same system so I am inclined to think it is a code change.

Ah, yep. I missed it when skimming. Sorry about that. And thanks for confirming.

I don’t have Linux so won’t be able to test on my end, but will tag @Mattches on this in hopes he can follow up here later.

Thank you for leaving the highly detailed report and opening an associated GH issue — really helps us out a lot. I’ve compiled all your information and have asked our Linux team to take a look to see if it is something we can address.

Will leave this thread open for now and will let you know when I have more information. Thank you again for reporting.

1 Like

Looks like this one is an upstream fix:>Ozone

Also experienced a similar crash on this with a login form that caused the “sign in with Google” pop-up to appear in a new window.

Happy to report that I have stopped experiencing this issue on Version 1.54.6 Chromium: 114.0.5735.35 (Official Build) nightly (64-bit)! If that doesn’t make sense given the changes between the last nightly I used and this version, then that could also help determine if the problem was elsewhere in my desktop environment all along.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.