Bug 229650

Summary: [GTK] facebook.com/watch or Facebook videos crash the web process
Product: WebKit Reporter: Amr Ibrahim <amribrahim1987>
Component: WebKitGTKAssignee: Nobody <webkit-unassigned>
Status: RESOLVED MOVED    
Severity: Normal CC: bugs-noreply, mcatanzaro
Priority: P3 Keywords: Gtk
Version: WebKit Nightly Build   
Hardware: PC   
OS: Linux   
See Also: https://github.com/intel/media-driver/issues/1132
Attachments:
Description Flags
Backtrace from the MiniBrowser none

Description Amr Ibrahim 2021-08-28 12:30:21 PDT
This bug affects GNOME Web 3.38.2 on WebKitGTK 2.32.3 or the MiniBrowser on Debian 11 Bullseye.

Steps to reproduce the bug:

0. Open GNOME Web or /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/MiniBrowser
1. Go to https://www.facebook.com/watch
2. Browse a bit or try to play a video
3. The web process crashes and there is nothing to see
Comment 1 Michael Catanzaro 2021-08-29 05:41:18 PDT
Works for me. As with any crash report, please post a backtrace taken with gdb. There are some instructions at https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces if you're not familiar with getting backtraces.
Comment 2 Amr Ibrahim 2021-08-29 06:25:44 PDT
Created attachment 436739 [details]
Backtrace from the MiniBrowser
Comment 3 Michael Catanzaro 2021-08-29 09:06:03 PDT
Comment on attachment 436739 [details]
Backtrace from the MiniBrowser

There is no backtrace here. Looks like you tried to get a backtrace from the UI process. You need to get a backtrace for the web process that is actually crashing.

Sadly Debian does not enable coredumpctl by default. If you had that available, then you could simply run 'coredumpctl gdb' after it crashes.
Comment 4 Amr Ibrahim 2021-10-14 13:38:24 PDT
Thanks for giving me a hint on how to debug this.

It turned out that the bug was in the intel-media-va-driver, and a workaround is to install intel-media-va-driver-non-free. The web process doesn't crash when the non-free driver is installed instead of the free one.

https://github.com/intel/media-driver/issues/1132

So this bug can be closed now.
Comment 5 Michael Catanzaro 2021-10-14 15:34:48 PDT
OK then.