After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 792460 - playbin deadlock
playbin deadlock
Status: RESOLVED DUPLICATE of bug 792341
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
1.10.2
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2018-01-12 11:33 UTC by Christoph Reiter (lazka)
Modified: 2018-01-13 10:24 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Python example (635 bytes, text/plain)
2018-01-12 11:33 UTC, Christoph Reiter (lazka) 		Details
gdb stacktrace (45.35 KB, text/plain)
2018-01-12 11:33 UTC, Christoph Reiter (lazka) 		Details

Description Christoph Reiter (lazka) 2018-01-12 11:33:00 UTC 
Created attachment 366723 [details]
Python example

Using GStreamer 1.12.4. Recent GStreamer has started deadlocking again when creating playbin elements, not sure when it started.

Attached is a small Python example which can be passed an MP3:

gst-crash.py a.mp3

Also attached a stacktrace of the hang.
Comment 1 Christoph Reiter (lazka) 2018-01-12 11:33:27 UTC 
Created attachment 366724 [details]
gdb stacktrace
Comment 2 Nicolas Dufresne (ndufresne) 2018-01-12 14:31:24 UTC 
Could this be because of this regression ?

https://bugzilla.gnome.org/show_bug.cgi?id=792341
Comment 3 Christoph Reiter (lazka) 2018-01-12 14:33:51 UTC 
Thanks. I'll try with a revert of two commits mentioned there.
Comment 4 Christoph Reiter (lazka) 2018-01-12 20:54:12 UTC 
Bisect on the gstreamer master branch:

d915dd4b20ffdcb417ea4b46a8dd9010c7ce7bf9 is the first bad commit
commit d915dd4b20ffdcb417ea4b46a8dd9010c7ce7bf9
Author: Edward Hervey <edward@centricular.com>
Date:   Thu Nov 16 10:47:46 2017 +0100

    gstpad: Make pad (de)activation atomic
Comment 5 Sebastian Dröge (slomo) 2018-01-13 10:24:40 UTC 

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