GST_PAD_PROBE_HANDLED

[marc lievens]

Hi,

We are extracting video parts from soure file to destination file via
multiple seeks, which work great.
The pipeline is :

    source | matroskademux | queue | h264parse | matroskamux | filesink and
is executed on windows 10 with gstreamer 1.10.2

On pad-added signal we add a probe ( settings GST_PAD_PROBE_TYPE_BUFFER |
GST_PAD_PROBE_TYPE_BUFFER_LIST).
The probe is added on sink of queue. On probe callback the follwing code is
executed:

    GstMessage* msg =
gst_message_new_application(GST_OBJECT_CAST(pipeline),
gst_structure_new_empty("ExPrerolled"));
    gst_bus_post(pipe_.bus, msg);
    gst_pad_remove_probe(pad, GST_PAD_PROBE_INFO_ID(info));
    GST_PAD_PROBE_INFO_FLOW_RETURN (info) = GST_FLOW_FLUSHING;
    return GST_PAD_PROBE_HANDLED;

Now it seems that when GST_PAD_PROBE_HANDLED is returned a memory leak is
seen and when GST_PAD_PROBE_DROP is returned the memory leak disapeared.

Are we doing something wrong or is there indeed some kind of memory leak?
When message" ExPrerolled" is received seeking starts to extract video.

Thanks in advance,
Marc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20170404/c6cc232a/attachment.html>