[Bug 719893] multiqueue: spams overrun signal

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=719893
  GStreamer | gstreamer (core) | git

--- Comment #3 from Per Johansson <perxjoh at axis.com> 2013-12-20 12:38:10 UTC ---
(In reply to comment #2)
> Review of attachment 263572 [details]:
> 
> I don't think this is correct. Now you'll only ever emit the signal for
> bytes/time overruns, not buffer overruns.

I think we should then start by determine what the purpose of the overrun
signal is. What use case is it supposed to solve. As I see it overrun should be
used to handle the case where the pipeline might deadlock. For example  when
one queue is full while an other is empty, and a muxer with collect pads are
waiting for buffers from both before continuing.
If overrun is emitted as soon as one queue reaches it's buffer limit, overrun
will be spammed when the source produces buffers faster than the sink consumes
them.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.