GNOME Bugzilla – Bug 758276
queue2: custom http-headers event sent by souphttpsrc causes g_warning in ring-buffer mode
Last modified: 2015-11-18 12:00:12 UTC
In gst_soup_http_src_got_headers_cb(), the headers event is created, and upon next create(), it's being pushed before buffer. The queue2 in ring-buffer mode prints g_warning then, causing crash if debugging (G_DEBUG=fatal-warnings). This should be changed to GST_WARNING or even lower. Reproduction steps: $ gst-launch-1.0 souphttpsrc location=http://kernel.org ! queue2 ring-buffer-max-size=1024000 ! fakesink Setting pipeline to PAUSED ... Pipeline is PREROLLING ... ** (gst-launch-1.0:5590): WARNING **: Unexpected event of kind custom-downstream-sticky can't be added in temp file of queue queue2-0 Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstSystemClock Got EOS from element "pipeline0". Execution ended after 0:00:00.106387959 Setting pipeline to PAUSED ... Setting pipeline to READY ... Setting pipeline to NULL ... Freeing pipeline ...
commit ffecef4fa003101f9eb7f9bb2daf0effe6591fe6 Author: Tim-Philipp Müller <tim@centricular.com> Date: Wed Nov 18 11:46:45 2015 +0000 queue2: don't print criticals when receiving custom events in ring buffer mode Downgrade from g_warning to GST_WARNING log message. https://bugzilla.gnome.org/show_bug.cgi?id=758276 t