[Bug 774846] asfdemux: Timeouts with corrupted files

[GStreamer (GNOME Bugzilla)]

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

Edward Hervey <bilboed at bilboed.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|git master                  |1.11.1

--- Comment #23 from Edward Hervey <bilboed at bilboed.com> ---
commit 48a493070aec4b5426723a4a27f14eba107779cf
Author: Edward Hervey <edward at centricular.com>
Date:   Tue Nov 22 17:14:44 2016 +0100

    asfdemux: Handle EOS in push-mode on corrupted files

    It is possible no streams were activated when receiving EOS, if so
    handled it as if we hadn't seen the header

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

commit e7ff86665a8e2c77a676546accf07f44b005f0dc
Author: Edward Hervey <edward at centricular.com>
Date:   Tue Nov 22 16:56:04 2016 +0100

    asfdemux: FILE headers are mandatory in the header

    As per the specification, also avoids ending up trying to play a
    file with plenty of un-initialized values.

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

commit cc04255e946f28acb4a60cc570c0c460c2f0154f
Author: Edward Hervey <edward at centricular.com>
Date:   Tue Nov 22 16:54:26 2016 +0100

    asfdemux: Handle incomplete header in pull mode

    pulling headers is meant to complete as a whole. If we don't have
    enough data, it's an error.

    Avoids pipeline hangs on corrupted files

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

commit 45c7826d76dfcb94cebbc57208c553d432fdc4a9
Author: Edward Hervey <edward at centricular.com>
Date:   Tue Nov 22 16:22:49 2016 +0100

    asfdemux: Handle issues with "empty" files

    In some corrupted files, we could end up with no actual streams
    being exposed.

    In those cases, make sure we properly propagate the failure all
    the way to the loop function. This avoids ending up in cases where
    we are neither EOS'd nor ERROR'd out from a pipeline point of view.

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

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.