Hi all,
Almost a couple of years ago, I created this post regarding a memory leak when using hardware encoders in JetPack 5.1.1.
I did a similar test in the following scenario:
• Hardware Platform (Jetson / GPU): Xavier AGX Devkit
• JetPack Version (valid for Jetson only): 5.1.5
• Check the RSS memory using the following script::
rss_memory.txt (352 Bytes)
To check the memory leak, I followed the next steps:
- Install the GStreamer Daemon (GstD) as explained in GStreamer Daemon GstD
- Install gst-perf GitHub - RidgeRun/gst-perf: GStreamer element to measure framerate, bitrate and CPU usage.
- Open three terminals. In terminal 1., run
gstd
- In terminal two, run the following
test
script
test.txt (589 Bytes) - In terminal three, run the
rss_memory
script.
I ran the test for two hours and got the following graphic:
Then, I change the nvv4l2h265enc
for the x265enc
to confirm that the memory leak is only related to the hardware encoder. I got the following:
Based on the above results, the hardware encoder still has a memory leak.
According to the NVIDIA mod, the memory leak was resolved:
Questions for the NVIDIA team:
- Could you please try to reproduce the memory from your side?
- If you could confirm that the memory leak is present, is there a possibility that you can share the solution mentioned in Memory leak in JetPack 5.1.1 when repeating the start/stop cycle of a GStreamer pipeline including nvvideoconvert and nvv4l2h264/vp9 encoders - #8 by yuweiw
Regards!
Eduardo Salazar
Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com/
Website: www.ridgerun.com