GStreamer pipeline hangs after hours due to errors

[streakflash]

Hi,
I confirm that the patch has resolved the issue with the nvv4l2h265enc encoder. Thank you for that.

Now since first issue has gone, can you give advice on the camera’s failure ?
I have tested both cameras simultaneously using gstreamer pipeline shown below on a regular laptop running Ubuntu 20.04 and no faulty detected so far, but cameras are guaranteed to fail on short period of time while using the same pipeline on Jetson Xavier NX.

gst-launch-1.0 -e \
    v4l2src device=/dev/video0 name=source_1 ! 'video/x-raw,format=YUY2,width=1920,height=1080,framerate=30/1' ! videoconvert ! xvimagesink sync=false name=sink_primary \
    v4l2src device=/dev/video1 name=source_2 ! 'video/x-raw,format=YUY2,width=1920,height=1080,framerate=30/1' ! videoconvert ! xvimagesink sync=false name=sink_secondary

I’ve tried tricks from the these topics, still couldnt resolve the issue

Jetson Nano USB 3.0 Bandwidth Issue

That seems really low compared to the rest of the SOC. Note, if you have less than the required 5.1V components will run hotter as they try to compensate. Also the stock cooler has been shown to be insufficient in certain loads, if the issue continues you might want to consider an aftermarket one. I’ve noticed that when the SOC is drawing it’s max power, USB is one of the first functions to crash.

Problematic USB behavior

Running into some new and strange USB behavior using the USB 3.0 E-Consystems See3Cam_130 UVC Camera. I am recieving inconsistent and intermittent and V4L2 errors like: Could not read from recource Could not identify device No such file or directory Failed to allocate required memory This particular camera and Nano have worked together for several weeks until today when these errors began coming up randomly at different times when using Gstreamer and other tools utilizing V4L2. The system w…