[Bug 650416] New: [h264parse] Assertion failure: nal_size >=2

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=650416
  GStreamer | gst-plugins-bad | git

           Summary: [h264parse] Assertion failure: nal_size >=2
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-bad
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: bens at alum.mit.edu
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Created an attachment (id=187977)
 --> (https://bugzilla.gnome.org/attachment.cgi?id=187977)
I tried GST_DEBUG=5 but had to stop it when the log file hit 7 GB.

I ran this pipeline, which until recently was failing due to #650323

./gst-jhbuild run gst-launch-0.10 filesrc location=clip.mts ! mpegtsdemux
name=demux ! ac3parse ! queue ! matroskamux name=mux ! filesink
location=clip.mkv . demux. ! h264parse ! queue ! mux.

The pipeline runs for a long time, as it should because clip.mts is a 3.5GB
AVCHD file, and then fails with

** (gst-launch-0.10:10133): CRITICAL **: gst_h264_parse_process_nal: assertion
`nal_size >= 2' failed

Where I come from, an assertion failure is always a bug.

Unfortunately, a 90 MB segment from the beginning of the file appears to be
insufficient to trigger the failure, which does not occur until 2.9 GB have
been written to clip.mkv.

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