[gstreamer-bugs] [Bug 328491] New: Sending FLUSH_START blocks in GstCollectPads

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=328491
 GStreamer | gstreamer (core) | Ver: 0.10.2

           Summary: Sending FLUSH_START blocks in GstCollectPads
           Product: GStreamer
           Version: 0.10.2
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: manauw at skynet.be
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


To reproduce:
Consider a GstCollectPads based-element (e.g. muxer) whose pads are being fed
by various task-based elements, say GstQueue in sequel.
Very likely, all but one of these tasks are always kept waiting in
gst_collect_pads_chain as the one-element queue (for the pad) has a buffer.
Now consider a FLUSH_START going through the pipeling (e.g. part of FLUSHing
seek); it arrives at GstQueue, which forwards the event to unblock its task (if
needed).  GstCollectPads ignores this, keeps the task waiting, after which
GstQueue tries to gst_pad_pause_task(), which blocks the event'ing thread.
Also, if any of the "feeding" tasks does stop, the "imbalance" keeps
GstCollectPads waiting, blocking the pipeline.


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.