[Bug 666053] baseparse: prevent excessively high memory usage with large streams

[GStreamer (bugzilla.gnome.org)]

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

Tim-Philipp Müller <t.i.m> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
            Version|0.10.x                      |git
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |1.1.1

--- Comment #18 from Tim-Philipp Müller <t.i.m at zen.co.uk> 2012-10-28 20:03:05 UTC ---
Pushed this with minor changes (no need to use gst_scale_* to determine the min
byte distance; some comments; use LOG level for 'already have entries up to
offset N').

 commit 37a72b1a82143f47dc78933e209a3cb0e1f358d0
 Author: Vincent Penquerc'h <vincent.penquerch at collabora.co.uk>
 Date:   Wed Jun 13 13:02:48 2012 +0100

    baseparse: prevent excessively high memory usage with long streams

    Large streams would index one frame every second, which can get quite
    large with multi-hour streams, so add an additional byte-based
    minimum distance as well, which will kick in for long streams
    and make sure we never have more than a couple of thousand index
    entries.

    https://bugzilla.gnome.org/show_bug.cgi?id=666053

-- 
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.