H264parse process backlog bug

I’m randomly getting the following with 1.23.90 and 1.24.1 (which causes my app to crash completely):

**
ERROR:../gst/videoparsers/gsth264parse.c:1776:gst_h264_parse_process_backlog: assertion failed: (h264parse->nal_backlog->len > 0)
Bail out! ERROR:../gst/videoparsers/gsth264parse.c:1776:gst_h264_parse_process_backlog: assertion failed: (h264parse->nal_backlog->len > 0)

It doesn’t do this with 1.22.11. However, it appears there are webrtcbin related memory leaks in that (and earlier) versions that don’t appear to be there in newer versions, hence the reason I want to run newer versions.

I was wondering if anyone has ran into this problem and whether there’s a workaround?

I haven’t looked too close at the details, but there’s been some recent changes to this gst_h264_parse_process_backlog function with 6093. Perhaps it’s related?

Small update. I can reproduce this using gst-launch-1.0, so it’s not just a problem in my app. The pipeline is:

gst-launch-1.0 rtspsrc location=rtsp://10.16.14.207/s0 ! parsebin ! decodebin ! autovideosink

The rtsp url is a UniFi UVC camera (firmware UVC.v3.5.2.63.5d0239d.161121.1655)

See h264parse element hangs with some video streams (#3436) · Issues · GStreamer / gstreamer · GitLab

Can you make a stream available that reproduces this problem so we can be sure that whatever fix ends up happening for this also covers your stream?

I think I have a gdp file that will work. I’ll post it on the issue you linked to.

1 Like