Crash when go youtube

Description of the issue: I go to youtube with brave, It crashed
How can this issue be reproduced?

  1. go to https://youtube.com
  2. crash

Expected result:
Loading site

Brave Version( check About Brave):
1.47.22 Chromium: 107.0.5304.68 (Official Build) nightly (64-bit)

Additional Information: I use hardware accelration on wayland and brave-nightly --enable-features=UseOzonePlatform --ozone-platform=wayland
Use arch linux and wayland, install via AUR (brave-nightly-bin)

1 Like

@misile,
Thank you for reaching out to us.

Does this happen every time you visit Youtube or is it intermittent? If you disable Hardware Acceleration in the browser do you get the same result? If you test this on Brave stable, do you get the same result?

It worked with same setting on previous brave nightly build, so It maybe work in brave-stable (not tested)
I turned off hardware accelerated but crashed

wait a sec, I using brave-nightly-bin 1.47.22, so not latest version
I will update and try again now

I updated but not worked

@misile,
I will report this to the team but please remember that issues/bugs with Nightly are expected and frequent. Can you go to brave://crashes and send us the crash report for these events? Additionally, please tell me the crash report ID given to you once the crash is submitted so that we can look these events up easily.

Thank you

Crash ID: 9a200100-c482-0f09-0000-000000000000
@Mattches

Having the same issue with the latest nightly (and also the previous 2 or 3 nightlies)
It’s not just youtube by the way, it happens on other websites too.
Error code is : SIGSEGV

Thank you both for the information. Looks like we can reproduce and are aware of the issue. Will respond when I have more information. Appreciate your patience.

1 Like

We’ve released a fix for this — already available for Linux builds, builds for other OS should be up shortly. Note that this is a public release so you should be prompted to update your Nightly browser in the next couple of hours.

Thank you

2 Likes

it works now with the fix @Mattches thank you that was really fast

1 Like