[Bug 767169] adaptivedemux: avoid possible deadlock while destroying old sources

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=767169

Tim-Philipp Müller <t.i.m at zen.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |t.i.m at zen.co.uk
         Resolution|---                         |FIXED
   Target Milestone|git master                  |1.9.2

--- Comment #1 from Tim-Philipp Müller <t.i.m at zen.co.uk> ---
Thanks for the patch. I believe this was also fixed as part of:

commit 62ca319927c15c984fb587e357cfbbf994eca717
Author: Jan Schmidt <jan at centricular.com>
Date:   Wed Jul 13 23:02:10 2016 +1000

    adaptivedemux: Drop the manifest lock during outbound actions

    Drop the manifest lock when performing actions that might
    call back into adaptivedemux and trigger deadlocks, such
    as adding/removing pads or sending in-band events (EOS).

    Unlock the manifest lock when changing the child bin state to
    NULL, as it might call back to acquire the manifest lock when
    shutting down pads.

    Drop the manifest lock while pushing events.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.