Please provide complete information as applicable to your setup.
• Hardware Platform (Jetson / GPU) Jetson Nano
• DeepStream Version 5.1
• JetPack Version (valid for Jetson only) 4.5.1
• TensorRT Version 7
• NVIDIA GPU Driver Version (valid for GPU only)
• Issue Type( questions, new requirements, bugs) Memory Leak in DeepStream plugins
• How to reproduce the issue ? (This is for bugs. Including which sample app is using, the configuration files content, the command line used and other details for reproducing) GST_TRACERS=‘leaks’ GST_DEBUG=‘GST_TRACER:7’ gst-launch-1.0 videotestsrc num-buffers=600 ! nvvidconv ! ‘video/x-raw(memory:NVMM)’ ! nvegltransform ! nveglglessink -e
• Requirement details( This is for new requirement. Including the module name-for which plugin or for which sample application, the function description) I have a Deepstream application that runs 24h/7 and it carshes because systems goes out of memory. The application has memory leaks that are situated at DeepStream plugins level. for example : I run this simple pipeline and GST_TRACERS=‘leaks’ GST_DEBUG=‘GST_TRACER:7’ gst-launch-1.0 videotestsrc num-buffers=600 ! nvvidconv ! ‘video/x-raw(memory:NVMM)’ ! nvegltransform ! nveglglessink -e
and i get the following
GST_TRACERS=‘leaks’ GST_DEBUG=‘GST_TRACER:7’ gst-launch-1.0 videotestsrc num-buffers=600 ! nvvidconv ! ‘video/x-raw(memory:NVMM)’ ! nvegltransform ! nveglglessink -e
0:00:00.062790208 17139 0x5596f56800 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register: update existing feature 0x5596d234c0 (latency)
0:00:00.062882710 17139 0x5596f56800 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register: update existing feature 0x5596d23400 (log)
0:00:00.062928127 17139 0x5596f56800 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register: update existing feature 0x5596d23340 (rusage)
0:00:00.062966774 17139 0x5596f56800 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register: update existing feature 0x5596d23280 (stats)
0:00:00.063002712 17139 0x5596f56800 DEBUG GST_TRACER gsttracer.c:164:gst_tracer_register: update existing feature 0x5596d231c0 (leaks)
0:00:00.063159903 17139 0x5596f56800 TRACE GST_TRACER gsttracerrecord.c:111:gst_tracer_record_build_format: object-alive.class, type-name=(structure)“value,\ type=(type)gchararray,\ related-to=(GstTracerValueScope)GST_TRACER_VALUE_SCOPE_PROCESS;”, address=(structure)“value,\ type=(type)gpointer,\ related-to=(GstTracerValueScope)GST_TRACER_VALUE_SCOPE_PROCESS;”, description=(structure)“value,\ type=(type)gchararray,\ related-to=(GstTracerValueScope)GST_TRACER_VALUE_SCOPE_PROCESS;”, ref-count=(structure)“value,\ type=(type)guint,\ related-to=(GstTracerValueScope)GST_TRACER_VALUE_SCOPE_PROCESS;”, trace=(structure)“value,\ type=(type)gchararray,\ related-to=(GstTracerValueScope)GST_TRACER_VALUE_SCOPE_PROCESS;”;
0:00:00.063210790 17139 0x5596f56800 DEBUG GST_TRACER gsttracerrecord.c:125:gst_tracer_record_build_format: new format string: object-alive, type-name=(string)%s, address=(gpointer)%p, description=(string)%s, ref-count=(uint)%u, trace=(string)%s;
0:00:00.063353241 17139 0x5596f56800 TRACE GST_TRACER gsttracerrecord.c:111:gst_tracer_record_build_format: object-refings.class, ts=(structure)“value,\ type=(type)guint64,\ related-to=(GstTracerValueScope)GST_TRACER_VALUE_SCOPE_PROCESS;”, type-name=(structure)“value,\ type=(type)gchararray,\ related-to=(GstTracerValueScope)GST_TRACER_VALUE_SCOPE_PROCESS;”, address=(structure)“value,\ type=(type)gpointer,\ related-to=(GstTracerValueScope)GST_TRACER_VALUE_SCOPE_PROCESS;”, description=(structure)“value,\ type=(type)gchararray,\ related-to=(GstTracerValueScope)GST_TRACER_VALUE_SCOPE_PROCESS;”, ref-count=(structure)“value,\ type=(type)guint,\ related-to=(GstTracerValueScope)GST_TRACER_VALUE_SCOPE_PROCESS;”, trace=(structure)“value,\ type=(type)gchararray,\ related-to=(GstTracerValueScope)GST_TRACER_VALUE_SCOPE_PROCESS;”;
0:00:00.063397461 17139 0x5596f56800 DEBUG GST_TRACER gsttracerrecord.c:125:gst_tracer_record_build_format: new format string: object-refings, ts=(guint64)%lu, type-name=(string)%s, address=(gpointer)%p, description=(string)%s, ref-count=(uint)%u, trace=(string)%s;
Setting pipeline to PAUSED …
Using winsys: x11
Pipeline is PREROLLING …
Got context from element ‘eglglessink0’: gst.egl.EGLDisplay=context, display=(GstEGLDisplay)NULL;
Pipeline is PREROLLED …
Setting pipeline to PLAYING …
New clock: GstSystemClock
Got EOS from element “pipeline0”.
Execution ended after 0:00:19.999954128
Setting pipeline to PAUSED …
Setting pipeline to READY …
Setting pipeline to NULL …
Freeing pipeline …
0:00:20.334556281 17139 0x5596f56800 TRACE GST_TRACER :0:: object-alive, type-name=(string)GstEGLImageAllocator, address=(gpointer)0x5596fd7d70, description=(string), ref-count=(uint)2, trace=(string);
0:00:20.334628678 17139 0x5596f56800 TRACE GST_TRACER :0:: object-alive, type-name=(string)GstEglGlesSink, address=(gpointer)0x5596fc9180, description=(string), ref-count=(uint)1, trace=(string);
0:00:20.334665502 17139 0x5596f56800 TRACE GST_TRACER :0:: object-alive, type-name=(string)GstPad, address=(gpointer)0x5596f6ad60, description=(string)eglglessink0:sink, ref-count=(uint)1, trace=(string);
** (gst-launch-1.0:17139): WARNING **: 11:29:31.599: Leaks detected
Is there a way to debug fix any leaks on nvidia Deepstream plugins?