When i run above program with valgrind for leaks, it throws possibly lost
and still reachable errors.
Is those leaks are major one or i can ignore?
please let me know the reason for leaks and ways to avoid the leak.
376 bytes in 1 blocks are possibly lost in loss record 1,408 of 1,438
==5458== at 0x4C29B78: realloc (vg_replace_malloc.c:785)
==5458== by 0x5887B65: g_realloc (in /usr/lib64/libglib-2.0.so.0.5000.3)
==5458== by 0x56137D8: ??? (in /usr/lib64/libgobject-2.0.so.0.5000.3)
==5458== by 0x5618254: g_type_register_static (in
==5458== by 0x55F8E3D: g_enum_register_static (in
==5458== by 0x537C8DE: gst_promise_result_get_type (gstenumtypes.c:1420)
==5458== by 0x52E13CC: init_post (gst.c:769)
==5458== by 0x588E797: g_option_context_parse (in
==5458== by 0x52E1F2E: gst_init_check (gst.c:427)
==5458== by 0x52E1F76: gst_init (gst.c:471)
==5458== by 0x400876: main (mem.c:7)
==5458== LEAK SUMMARY:
==5458== definitely lost: 0 bytes in 0 blocks
==5458== indirectly lost: 0 bytes in 0 blocks
==5458== possibly lost: 4,068 bytes in 60 blocks
==5458== still reachable: 416,782 bytes in 1,426 blocks
==5458== of which reachable via heuristic:
==5458== length64 : 80 bytes in 2 blocks
==5458== newarray : 1,552 bytes in 17
==5458== suppressed: 0 bytes in 0 blocks
==5458== Reachable blocks (those to which a pointer was found) are not
==5458== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==5458== For counts of detected and suppressed errors, rerun with: -v
==5458== ERROR SUMMARY: 60 errors from 60 contexts (suppressed: 0 from 0)
On Tue, 2018-10-09 at 03:51 -0500, vittalprasad wrote:
> I'm new to Gstreamer frame-work. i have written sample program to
> check memory leaks.
> When i run above program with valgrind for leaks, it throws possibly
> lost and still reachable errors.
> Is those leaks are major one or i can ignore?
You can ignore them, they are one-time allocations by the GObject type
This is one of the suppression files we use in GStreamer when running
unit tests through valgrind, you might find it useful: