I’m able to send rtp streams across the network using nvv4l2h265enc and receive rtp streams in gstreamer pipeline for c program code;
To adapt to the poor situation of the network,the stream resolution will change:[1280x960,640x480,480x360];
but after change resolution test 488 times, nvv4l2h265enc crashed
Hi,
Do you re-initialize the gstreamer pipeline when resolution changes? By default it does not support runtime resolution change in nvv4l2h265enc. When resolution changes, please terminate the original pipeline and re-initialize a new one.
And in my another test,delete send eos,it repeated 14276 times and crashed,locked on gst_pad_stop_task
steps:
1 gst_element_set_state(rts->pipeline, GST_STATE_NULL);
2 gst_object_unref(rts->pipeline);
3 g_usleep(1000000);
4 reinitialize pipeline
i test ,it also occure memory leak !
i test on 3 tx2;one repeat restart gstreamer pipeline 76449 times,memory from 1% to 37.8%;another repeat restart gstreamer pipeline 81399 times,memory from 1% to 25.4%;the third repeat restart gstreamer pipeline 55893 times,memory from 1% to 28.4%;
the memory lead can test on my attach[gst-20220112.tar.gz on the above reply],i change nvv4l2h265enc,omxh265enc,all test this memory leak.
And if you stay on r32.5.0, please follow the steps to rename libv4l2_nvargus.so. Some issues are reported with the prebuilt lib and please rename it so that is is not loaded.
test code & gcc
huilian@huilian-desktop:~/xxw/test1$ ls
a.out test.cpp
huilian@huilian-desktop:~/xxw/test1$ cat test.cpp include include include include <gst/gst.h>
using namespace std;
Hi,
Do you upgrade to r32.6.1 and do the test? Since we don’t see significant leak on r32.6.1, you may consider to upgrade to the version. We are deprecating omx plugins, but if the plugins work fine in your use-case, you may still consider to use it.