Gstreamer1.0 : memory leak

Rohan0993 rohan.chawhan at
Mon May 20 11:14:01 UTC 2019

I am trying to check the memory leakage of my program using Valgrind.

Note: my program contains an FSM which is polled at every 200ms.(mentioning
this because I think this might have something to do with the leaks)

I have executed the following command and created the log file.

*valgrind --leak-check=full --track-origins=yes --verbose
--log-file=valgrind_test.log ./foo*

I see there are leaks in the gst library, and 90% of them are following the
same route/path as given below

*==9890== 96 bytes in 1 blocks are possibly lost in loss record 2,341 of
==9890==    at 0x4C30035: calloc (in
==9890==    by 0x66D96B0: g_malloc0 (in /usr/lib64/
==9890==    by 0x69CB421: ??? (in /usr/lib64/
==9890==    by 0x69CB5CA: ??? (in /usr/lib64/
==9890==    by 0x69D1062: g_type_register_fundamental (in
==9890==    by 0x6CBADD1: gst_fraction_get_type (gstvalue.c:7428)
==9890==    by 0x6CBB0B5: _priv_gst_value_initialize (gstvalue.c:7527)
==9890==    by 0x6C23B50: init_post (gst.c:777)
==9890==    by 0x66E011F: g_option_context_parse (in
==9890==    by 0x6C2462E: gst_init_check (gst.c:427)
==9890==    by 0x6C24676: gst_init (gst.c:471)
==9890==    by 0x5546CC: main (foo.cpp:97)*

how to find what this mean and solve this 

*==9890==    by 0x69CB421: ??? (in /usr/lib64/*

Sent from:

More information about the gstreamer-devel mailing list