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 669826 - [pitivi] [discoverer] Deadlocks when loading a project and discovering sources
[pitivi] [discoverer] Deadlocks when loading a project and discovering sources
Status: RESOLVED DUPLICATE of bug 681015
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Reported: 2012-02-10 18:43 UTC by Jean-François Fortin Tam
Modified: 2013-03-02 23:59 UTC
See Also:
GNOME target: ---
GNOME version: ---

gdb output (74.67 KB, text/plain)
2012-02-10 18:43 UTC, Jean-François Fortin Tam
gdb output from all threads (137.39 KB, text/plain)
2012-02-12 15:05 UTC, Jean-François Fortin Tam

Description Jean-François Fortin Tam 2012-02-10 18:43:25 UTC
Created attachment 207286 [details]
gdb output

In the GES version of pitivi, with my "droid mgs" project, I sometimes experience the following:

1. start pitivi
2. load the project
3. the deadlock occurs. This means the UI waits forever after the discoverer, so the progressbar is shown (indicated that the import process is supposedly started) but it stays empty.

Restarting the pitivi and trying again usually works. This seems to occur randomly, it might be a race condition of some kind. The only hint I have is the following gdb trace.
Comment 1 Jean-François Fortin Tam 2012-02-10 18:47:00 UTC
Pitivi project file and media:
Comment 2 Vincent Penquerc'h 2012-02-12 12:39:27 UTC
Could you attach a backtrace from other threads as well, since it's a deadlock ?
eg: "thread apply all bt" instead of just "bt".
That thread is blocking on a lock in qtdemux but it might be only the victim rather than the culprit.
Is there a way to repro this with ges-launch from this tarball, or does one have to install Pitivi ?
Comment 3 Jean-François Fortin Tam 2012-02-12 15:05:43 UTC
Created attachment 207392 [details]
gdb output from all threads

Here's the requested "thread apply all bt".
Took me 5 tries (starting pitivi and loading the project) before the bug occured.
Comment 4 David Schleef 2012-02-22 03:14:47 UTC
Moving to NEW, as it is a bug.
Comment 5 Jean-François Fortin Tam 2013-03-02 23:59:56 UTC

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