[gstreamer-bugs] [Bug 552560] New: new "max-lateness" property on rtpbin / jitterbuffer

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=552560

  GStreamer | gst-plugins-bad | Ver: HEAD CVS
           Summary: new "max-lateness" property on rtpbin / jitterbuffer
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-bad
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: havard.graff at tandberg.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
                CC: wim.taymans at gmail.com
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Working with rtpbin and jitterbuffer, we sometimes have observed that with an
element downstream blocking the pipeline for some reason, the jitterbuffer can
end up buffering up "unlimited" buffers. If these buffers are high definition
video then memory-issues are short to follow. 

The proposed patch is not in any way a good solution to such a problem, since
it will hide the real cause of it and should in theory never be necessary for a
well written pipeline, however it can be thought of as a "security vent",
making sure that there is SOME limit to how big the jitterbuffer can grow, and
the sort of extra protection an application might want.

The idea is that you set a time (in ms) how late a buffer can be before it gets
dropped.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=552560.