Bug 229650 - [GTK] facebook.com/watch or Facebook videos crash the web process
Summary: [GTK] facebook.com/watch or Facebook videos crash the web process
Status: RESOLVED MOVED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Nightly Build
Hardware: PC Linux
: P3 Normal
Assignee: Nobody
URL:
Keywords: Gtk
Depends on:
Blocks:
 
Reported: 2021-08-28 12:30 PDT by Amr Ibrahim
Modified: 2021-10-16 09:24 PDT (History)
2 users (show)

See Also:

Attachments
Backtrace from the MiniBrowser (3.93 KB, text/plain)
2021-08-29 06:25 PDT, Amr Ibrahim 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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.