[Bug 762717] New: [mpegtsmux] m2ts-mode crashes (abort)

[GStreamer (GNOME Bugzilla)]

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

            Bug ID: 762717
           Summary: [mpegtsmux] m2ts-mode crashes (abort)
    Classification: Platform
           Product: GStreamer
           Version: git master
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-plugins-bad
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: tobias.modschiedler at cetitec.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

The following pipeline crashes with SIGABORT:

> gst-launch-1.0 filesrc location=big_buck_bunny_720p_1mb.mp4 ! qtdemux ! queue ! h264parse ! mpegtsmux m2ts-mode=true ! filesink location=test.ts

Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...

(gst-launch-1.0:5193): GStreamer-CRITICAL **: gst_buffer_resize_range:
assertion 'bufmax >= bufoffs + offset + size' failed

(gst-launch-1.0:5193): GStreamer-CRITICAL **: gst_buffer_resize_range:
assertion 'bufmax >= bufoffs + offset + size' failed
**
ERROR:mpegtsmux.c:1656:new_packet_m2ts: assertion failed: (out_buf)
zsh: abort (core dumped)  gst-launch-1.0 filesrc
location=big_buck_bunny_720p_1mb.mp4 ! qtdemux ! queue


Without m2ts-mode, things go smoothly:

> gst-launch-1.0 filesrc location=big_buck_bunny_720p_1mb.mp4 ! qtdemux ! queue ! h264parse ! mpegtsmux m2ts-mode=false ! filesink location=test.ts

Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Got EOS from element "pipeline0".
Execution ended after 0:00:00.008166108
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...

The file used for testing was downloaded from here:
http://www.sample-videos.com/video/mp4/720/big_buck_bunny_720p_1mb.mp4

This was tested on Arch Linux with Linux 4.4.1-2-ARCH

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