gstreamer/plugins
Stian Selnes d03bd54780 queue: Fix race when calculating cur_level.time
On the first buffer, it's possible that sink_segment is set but
src_segment has not been set yet. If this is the case, we should not
calculate cur_level.time since sink_segment.position may be large and
src_segment.position default is 0, with the resulting diff being larger
than max-size-time, causing the queue to start leaking (if
leaky=downstream).

One potential consequence of this is that the segment event may be
stored on the srcpad before the caps event is pushed downstream, causing
a g_warning ("Sticky event misordering, got 'segment' before 'caps'").

https://bugzilla.gnome.org/show_bug.cgi?id=773096
2016-10-20 14:14:20 +03:00
..
elements queue: Fix race when calculating cur_level.time 2016-10-20 14:14:20 +03:00
tracers stats: Fix warning 2016-10-14 17:30:01 +02:00
Makefile.am tracer: initial prototype for the tracing subsystem 2015-10-05 20:59:39 +02:00
meson.build meson: Build tracers 2016-09-26 18:27:00 -03:00