dbus valgrind memcheck

[Ernast Sevo]

Hello!

I am quite new to DBus and have been writing an application that uses DBus.
To be safe I have been putting my application through some checks with Valgrind
and I get the following output:

==323==
==323== HEAP SUMMARY:
==323==     in use at exit: 12,955 bytes in 63 blocks
==323==   total heap usage: 2,384 allocs, 2,321 frees, 3,370,920 bytes allocated
==323==
==323== 2,428 bytes in 27 blocks are still reachable in loss record 1 of 3
==323==    at 0x4833ACC: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-arm-linux.so)
==323==
==323== 4,510 bytes in 22 blocks are still reachable in loss record 2 of 3
==323==    at 0x483577C: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-arm-linux.so)
==323==
==323== 6,017 bytes in 14 blocks are still reachable in loss record 3 of 3
==323==    at 0x483587C: realloc (in
/usr/lib/valgrind/vgpreload_memcheck-arm-linux.so)
==323==
==323== LEAK SUMMARY:
==323==    definitely lost: 0 bytes in 0 blocks
==323==    indirectly lost: 0 bytes in 0 blocks
==323==      possibly lost: 0 bytes in 0 blocks
==323==    still reachable: 12,955 bytes in 63 blocks
==323==         suppressed: 0 bytes in 0 blocks
==323==
==323== For counts of detected and suppressed errors, rerun with: -v
==323== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

I have put a section of my code in a loop that runs about 100 times. I
have yet to definitely/
possibly/indirectly lose any bytes but I have been worried about the
still reachable byte count.
I have seen this value triple during certain runs which makes me think
its partially not me. And i know
that there are applications that dont explicitly free memory at before
the end of program execution and
was wondering if this was the case with DBus.

Any help is appreciated!

Thanks,

 Ernast