[Bug 787243] New: pad: probe returning HANDLED does not behave in the expected way

[GStreamer (GNOME Bugzilla)]

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

            Bug ID: 787243
           Summary: pad: probe returning HANDLED does not behave in the
                    expected way
    Classification: Platform
           Product: GStreamer
           Version: git master
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: mparisdiaz at gmail.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

Created attachment 359065
  --> https://bugzilla.gnome.org/attachment.cgi?id=359065&action=edit
pad: add test to check handled and drop probes

Hello,
I have come across that probes returning HANDLED do not behave as the current
doc says:
  @GST_PAD_PROBE_HANDLED: Data has been handled in the probe and will not be
    forwarded further. For events and buffers this is the same behaviour as
    %GST_PAD_PROBE_DROP (except that in this case you need to unref the buffer
    or event yourself). For queries it will also return %TRUE to the caller.
    The probe can also modify the #GstFlowReturn value by using the
     #GST_PAD_PROBE_INFO_FLOW_RETURN() accessor.
    Note that the resulting query must contain valid entries.
    Since: 1.6

The point is that if there is another probe in the same pad it is called after
the probe returning HANDLED (when not expected) and if this other probe returns
DROP we deal with a GstBuffer refcount problem.
In order to show this issue I have created a test where you can see:
GStreamer-CRITICAL **: gst_mini_object_unref: assertion 'mini_object->refcount
> 0' failed

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