GNOME Bugzilla – Bug 599484
resindvd: Deadlock from seeking
Last modified: 2018-11-03 13:04:43 UTC
Here is a backtrace that can be hit when triggering a seek at the exact moment that resindvdsrc is performing a seamless seek on itself. It boils down to a locking order problem between the stream lock and the state lock: Thread 8 is attempting to seek (and acquire the state lock) while holding the stream lock. Thread 1 is attempting to acquire the stream lock after sending a flushing seek (and while holding the state lock). I am not sure of the right way to fix it. (gdb) thread apply all bt
+ Trace 218536
Thread 1 (Thread 0xb6ce8aa0 (LWP 12583))
Not that the locking has changed much, but does this still apply?
Does it?
Yes, afaik - although it's quite hard to hit.
So let's keep this open properly then.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/14.