[Bug 787144] Memory leak in gstqtmux.c
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Mon Sep 4 09:09:55 UTC 2017
https://bugzilla.gnome.org/show_bug.cgi?id=787144
--- Comment #4 from Matej Knopp <matej.knopp at gmail.com> ---
If those are indeed different thread than it means that gst_qt_mux_collected is
called while GST_STATE_CHANGE_PAUSED_TO_READY, which, if happens, seams like a
bigger problem than the original leak.
Or perhaps the state is changed from thread that has
gst_qt_mux_pad_fragment_add_buffer in while the muxer sends out buffer? In
which case the solution would perhaps be to copy the array content to stack
before iterating over it in gst_qt_mux_pad_fragment_add_buffer and clear
pad->fragment_buffers before sending out the first buffer.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs
mailing list