GNOME Bugzilla – Bug 626581
[playbin2] regression: occasional deadlocks in streamsynchronizer
Last modified: 2010-08-12 10:08:33 UTC
Totem regularly locks up during music playback and goom visualisations, with git of GStreamer: (gdb) thread apply all bt
+ Trace 223192
Thread 6 (Thread 0x7f81677fd710 (LWP 12676))
Thread 4 (Thread 0x7f81728b7710 (LWP 15313))
Thread 1 (Thread 0x7f818a50a7e0 (LWP 10058))
Also seeing these (one per song / eos?), but don't know if that's related at all: (lt-totem:12331): GStreamer-CRITICAL **: Trying to dispose element vis_bin, but it is in PLAYING instead of the NULL state. You need to explicitly set elements to the NULL state before dropping the final reference, to allow them to clean up. This problem may also be caused by a refcounting bug in the application or some element.
Mark reported two problems on IRC yesterday which might be related. He had fixes for them. Otherwise I'll take a look at this later :)
Created attachment 167589 [details] [review] streamsynchronizer: prevent deadlock with _chain when deactivating pad Looks like there might be a deadlocking race in streamsynchronizer between pad deactivation and _chain. Current patch should remedy.
Comment on attachment 167589 [details] [review] streamsynchronizer: prevent deadlock with _chain when deactivating pad Makes sense, please push this
Hopefully following takes care of this: commit 9975a2d7b411967c965f6cef8fd4d7ea97f619f7 Author: Mark Nauwelaerts <mark.nauwelaerts@collabora.co.uk> Date: Wed Aug 11 12:49:40 2010 +0200 streamsynchronizer: prevent deadlock with _chain when deactivating pad Fixes #626581.