[Bug 762013] curlhttpsink: Problem in curlhttpsink when qtmux uses faststart, don't send empty buffers

[GStreamer (GNOME Bugzilla)]

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

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.7.2
            Summary|curlhttpsink: Problem in    |curlhttpsink: Problem in
                   |curlhttpsink when qtmux     |curlhttpsink when qtmux
                   |uses faststart              |uses faststart, don't send
                   |                            |empty buffers

--- Comment #2 from Tim-Philipp Müller <t.i.m at zen.co.uk> ---
Makes sense I think. I have modified your patch slightly to move the
GST_OBJECT_LOCK after the check, which avoids the need to unlock in your if
branch.

 commit 55ba6f1ee898a9acc1bbac8dd3c53885eb9fe285
 Author: David Fernandez <d.fernandezlop at gmail.com>
 Date:   Tue Feb 16 15:10:34 2016 +0100

    curlbasesink: don't send empty buffers

    Fixes problem in curlhttpsink when qtmux uses faststart.

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

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