Memory leak in JetPack 4.6.4 when repeating the start/stop cycle of a GStreamer pipeline including nvv4l2h265 encoder

[EduardoSalazar96]

Hi all,

This is related to the same memory leak described in Memory leak in JetPack 5.1.5 when repeating the start/stop cycle of a GStreamer pipeline including nvv4l2h265 encoder using a TX2 and JetPack 4.6.4.

NVIDIA provided a fix for JetPack 5.1.5 and we got the following results

So we would like to fix the leak in JetPack 4.6.4 and produce the same behavior as the image attached above.

Regards!
Eduardo Salazar
Embedded SW Engineer at RidgeRun

Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com/
Website: www.ridgerun.com

[DaneLLL]

Hi,
We would need to set up developer kit ad check. The fix should be required but need to test it.

[DaneLLL]

Hi,
Beside the fix, there is a patch for nvidconv on Jetpack 5. Please apply it:

diff --git a/gst-nvvidconv-1.0/gstnvvconv.c b/gst-nvvidconv-1.0/gstnvvconv.c
index 62f4dbd..6478aff 100644
--- a/gst-nvvidconv-1.0/gstnvvconv.c
+++ b/gst-nvvidconv-1.0/gstnvvconv.c
@@ -2591,10 +2591,12 @@
     tmp1 = tmp2;
   }
 
-  if (gst_caps_is_empty(tmp1))
+  if (gst_caps_is_empty(tmp1)) {
     ret = gst_caps_copy(filter);
-  else
+    gst_caps_unref (tmp1);
+  } else {
     ret = tmp1;
+  }
 
   if (!filter) {
     GstStructure *str;

[EduardoSalazar96]

Hello @DaneLLL

Thank you for the patches provided. However, we would like to apply these fixes to JetPack 4. Are these patches applicable to JetPack 4?

Regards!

[DaneLLL]

Hi,
Yes, please apply to Jetpack 4.