After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 653087 - [h264parse] Assertions on valid h264 streams when converting to stream-format=avc,alignment=nal
[h264parse] Assertions on valid h264 streams when converting to stream-format...
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
0.10.13
Other Linux
: Normal blocker
: 0.10.23
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-06-21 09:36 UTC by Sebastian Dröge (slomo)
Modified: 2011-06-21 10:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastian Dröge (slomo) 2011-06-21 09:36:36 UTC
gst-launch-0.10 videotestsrc ! x264enc ! h264parse ! "video/x-h264,stream-format=avc,alignment=nal" ! fakesink

Leads to assertions and the pipeline never prerolls:
** (gst-launch-0.10:12258): CRITICAL **: gst_byte_reader_masked_scan_uint32: assertion `(guint64) offset + size <= reader->size - reader->byte' failed

Using h264parse to convert the same from a h264 stream inside an MP4 file additionally gives this assertion:
ERROR:gsth264parse.c:551:gst_h264_parse_check_valid_frame: assertion failed: (prev_sc_pos >= 0)
Aborted
Comment 1 Mark Nauwelaerts 2011-06-21 10:59:55 UTC
commit 10bec5c08f15bb968f4bd4605f8418147d147977
Author: Mark Nauwelaerts <mark.nauwelaerts@collabora.co.uk>
Date:   Tue Jun 21 12:43:41 2011 +0200

    h264parse: avc input must either pass-through or be split into bytestream chunks
    
    ... since parsing code is not meant to receive avc data.
    
    Fixes #653087.


The assertion itself (though not really the proper behaviour) is avoided by:

commit 160207abb908b03cc4dbd3cafac083e8de0d9725
Author: Mark Nauwelaerts <mark.nauwelaerts@collabora.co.uk>
Date:   Tue Jun 21 12:41:47 2011 +0200

    h264parse: avoid bogus frame parsing state