GStreamer-CRITICAL gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed SPAM
Hey, I'm using gstreamer in an Nvidia Jetson TX2 and I have an app based on this code to process in opencv an rtsp stream without appsrc / appsink that drop the framerate a lot. This app was working just fine in gstreamer 1.14.5 which is the official nvidia release, but I recently updated to 1.16.2 to be able to use webrtc. Then the following warning popped up and I don't know where it came from (I didn't change any code):
GStreamer-CRITICAL **: 10:46:36.477: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed
GStreamer-CRITICAL **: 10:46:36.490: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed
GStreamer-CRITICAL **: 10:46:36.509: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed
GStreamer-CRITICAL **: 10:46:36.542: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed
GStreamer-CRITICAL **: 10:46:36.597: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed
GStreamer-CRITICAL **: 10:46:36.617: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed
GStreamer-CRITICAL **: 10:46:36.628: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed
This seems to appear for every single frame or at least several times per second and makes the terminal unreadable (and also seems to be linked to the stream since any pipeline that opens the stream generated by this one also gets the spam messages). Is this the same as #861 (closed)? I see it was fixed in !519 (merged) but I really doubt I can update to master in this board, is there a chance this can be fixed without updating? The program works fine, I just need to mute the error to be able to read the terminal.
Thanks!