[Bug 797147] New: queue deadlocks if it is connected to a

[GStreamer (GNOME Bugzilla)]

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

            Bug ID: 797147
           Summary: queue deadlocks if it is connected to a
    Classification: Platform
           Product: GStreamer
           Version: 1.14.2
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: joel at airwebreathe.org.uk
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

Created attachment 373662
  --> https://bugzilla.gnome.org/attachment.cgi?id=373662&action=edit
C demo application

A pipeline is created with the following structure...                 

                 +-----------------------------------------+                  
                 |               bin                       |                  
                 |                                         |                  
                 |                      -> ghost_for_queue | -> queue ->
fakesink
 videotestsrc -> | sink_ghost -> tee                       |                  
                 |                   -> ghost_for_fakesink | -> fakesink      
                 |                                         |                  
                 +-----------------------------------------+                  

If the queue branch is connected to the first tee request pad, the pipeline
will work correctly. If the queue branch is connected to the second tee request
pad, the pipeline will deadlock.

This works:

 $ gst-launch-1.0 videotestsrc ! \( tee name="T" \) T. ! queue ! fakesink
num-buffers=1 T. ! fakesink num-buffers=1

This deadlocks:

 $ gst-launch-1.0 videotestsrc ! \( tee name="T" \) T. ! fakesink num-buffers=1
T. ! queue ! fakesink num-buffers=1

I've also attached the source for a test application which assembles the same
pipeline.

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