Bug 270698 - [GStreamer] Crash after 10 seconds on watchdog thread due to hang in WebCore::deinitializeGStreamer/WebCore::unregisterPipeline
Summary: [GStreamer] Crash after 10 seconds on watchdog thread due to hang in WebCore:...
Status: RESOLVED DUPLICATE of bug 264824
Alias: None
Product: WebKit
Classification: Unclassified
Component: Media (show other bugs)
Version: WebKit Nightly Build
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-08 06:59 PST by Michael Catanzaro
Modified: 2024-03-08 09:40 PST (History)
3 users (show)

See Also:

Attachments
All-threads backtrace (42.29 KB, text/plain)
2024-03-08 06:59 PST, Michael Catanzaro 		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 Michael Catanzaro 2024-03-08 06:59:12 PST 
Created attachment 470247 [details]
All-threads backtrace

This is a sequel to bug #257551. With WebKitGTK 2.43.4 and GStreamer 1.22.10, the main thread deadlocks when calling WebCore::unregisterPipeline instead a call to WebCore::deinitializeGStreamer, causing the watchdog thread to crash the process after 10 seconds. However, the backtrace is different than it was in bug #257551. Backtrace attached.

Notably, only the main thread is using GStreamer here, which seems unusual. In the many other GStreamer deadlocks I've reported, there are usually at least two GStreamer threads visible in the backtrace. Perhaps some other thread left the mutex locked by mistake?

I've hit this crash three times in the past hour, but I don't know what website is triggering it.
Comment 1 Philippe Normand 2024-03-08 07:08:40 PST 
And you have the fix from #257551 or not?
Comment 2 Michael Catanzaro 2024-03-08 08:17:00 PST 
Yes, because that bug was closed on January 1 but I'm using WebKitGTK 2.43.4 which was released in February.
Comment 3 Philippe Normand 2024-03-08 09:37:56 PST 
(In reply to Michael Catanzaro from comment #2)
> Yes, because that bug was closed on January 1 but I'm using WebKitGTK 2.43.4
> which was released in February.

I was referring to https://commits.webkit.org/275032@main which landed on February 20th.
Comment 4 Philippe Normand 2024-03-08 09:40:24 PST 

*** This bug has been marked as a duplicate of bug 264824 ***