[Bug 762875] queue: unsatisfied min-threshold-time blocks ALLOCATION query, resulting in stalled pipeline after deinterlace's RECONFIGURE event

[GStreamer (GNOME Bugzilla)]

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|git master                  |1.13.2

--- Comment #7 from Olivier Crête <olivier.crete at ocrete.ca> ---
The problem is that the code to ignore the threshold was ignored if the head of
the queue was a query.. but the query got added to the queue. I think it's a
regression from one of the refactoring that happened, so I added a unit test to
prevent futurue problems.

commit 23b32d56008d364257d1d186da52650cb4475aa4 (HEAD -> master,
upstream/master)
Author: Olivier Crête <olivier.crete at collabora.com>
Date:   Thu Mar 1 16:19:09 2018 -0500

    queue: Ignore thresholds if a query is queued

    The queue gets filled by the tail, so a query will always be the tail
    object, not the head object. Also add a _peek_tail_struct() method to the
    GstQueueArray to enable looking at the tail.

    With unit test to prevent future regression.

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

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