[Bug 784911] aggregate: chain_internal function called from two different threads for the same pad

[GStreamer (GNOME Bugzilla)]

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

Olivier Crête <olivier.crete at ocrete.ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|git master                  |1.13.1

--- Comment #16 from Olivier Crête <olivier.crete at ocrete.ca> ---
Patches merged

commit 25ea37e7d9b54bb47218b1f7d7c51c4f56d25171
Author: Olivier Crête <olivier.crete at collabora.com>
Date:   Thu Jul 13 19:03:19 2017 -0400

    aggregator: Don't take flush lock from output thread

    Instead just take it in the chain function.

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

commit bb5a8ebec32b65d7ce8bbcb063020cc166fe57c3
Author: Olivier Crête <olivier.crete at collabora.com>
Date:   Thu Jul 13 18:38:34 2017 -0400

    aggregator: Don't block if adding to the tail of the queue

    If we're adding to the tail of the queue, it's because we're converting
    a gap event, so don't block there it means we're calling from the output
    thread.

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

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