[gstreamer-bugs] [Bug 579642] [oggdemux] handle broken ogg/vorbis files better

[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=579642

  GStreamer | gst-plugins-base | Ver: git

Wim Taymans changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #133419|none                        |committed
               Flag|                            |
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |0.10.24




------- Comment #5 from Wim Taymans  2009-05-12 08:45 UTC -------
commit 7e43c107546e29857f11773762e8891690c47e50
Author: Wim Taymans <wim.taymans at collabora.co.uk>
Date:   Tue Apr 28 11:24:19 2009 +0200

    oggdemux: fix abuse of ogg API, handle broken oggs

    When we feed the ogg sync layer, we need to feed it contiguous data even if
the
    sync layer did not consume all of it yet. This makes sure that it always
finds
    the next page even for more corrupted files. Use a different read_offset
for
    this purpose. since we now keep track of the sync layer, we don't have to
reset
    after finding a start of a page.

    Add some more debug info for the error paths.

    Only reset the sync layer when we perform a seek operation.

    Avoid failure when the next chain has no bos pages but instead simply
ignore it.

    when we receive unknown page serial numbers mid stream, don't fail but post
a
    warning and hope that we get back on track later.

    Fixes #579642


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