[Bug 787466] glimagesink: release buffers on GST_EVENT_FLUSH_START
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Sat Sep 9 21:56:20 UTC 2017
https://bugzilla.gnome.org/show_bug.cgi?id=787466
--- Comment #3 from Yuji Kuwabara <HHG01200 at nifty.ne.jp> ---
https://gstreamer.freedesktop.org/documentation/design/events.html
"... discards any buffers it is holding ..."
-----------------------------------------------
Flushing happens in two stages.
a source element sends the FLUSH_START event to the downstream peer element.
The downstream element starts rejecting buffers from the upstream elements. It
sends the flush event further downstream and discards any buffers it is holding
as well as return from the chain function as soon as possible. This makes sure
that all upstream elements get unblocked. This event is not synchronized with
the STREAM_LOCK and can be done in the application thread.
-----------------------------------------------
Please read
https://bugzilla.gnome.org/show_bug.cgi?id=787290
-----------------------------------------------
"gstglimagesink.c"
In gst_glimage_sink_event(), add handler for GST_EVENT_FLUSH_START .
(almost same as GST_STATE_CHANGE_PAUSED_TO_READY in
gst_glimage_sink_change_state())
I think this prevents deadlock in gst_omx_video_dec_loop() by releasing output
port.
-----------------------------------------------
--
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