dbus_bus_get loss record

[mwatts15]

This loss record popped up during testing. No explanation for it. On subsequent executions, the record doesn't show. There's no obvious functional problem associated.

==3832== Memcheck, a memory error detector
==3832== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==3832== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright info
==3832== Command: ../tagfs -o use_ino,attr_timeout=0 --drop-db --data-dir=/tmp/.acctest-tagfs-datadir-IPBZP5LLiI -g 0 -l /tmp/acctest-tagfs-log.out.f1CCEAH5wA -d /tmp/.acctest-tagfs-mountdir-vE0ZGRi2uT
==3832== Parent PID: 3830
==3832== 
==3832== 
==3832== HEAP SUMMARY:
==3832==     in use at exit: 12,535 bytes in 81 blocks
==3832==   total heap usage: 2,063 allocs, 1,982 frees, 1,335,748 bytes allocated
==3832== 
==3832== 567 (184 direct, 383 indirect) bytes in 1 blocks are definitely lost in loss record 74 of 77
==3832==    at 0x4C2CC70: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==3832==    by 0x5391145: dbus_message_new_empty_header (in /lib/x86_64-linux-gnu/libdbus-1.so.3.7.6)
==3832==    by 0x5394A2A: dbus_message_new_error (in /lib/x86_64-linux-gnu/libdbus-1.so.3.7.6)
==3832==    by 0x5397427: _dbus_pending_call_set_timeout_error_unlocked (in /lib/x86_64-linux-gnu/libdbus-1.so.3.7.6)
==3832==    by 0x53886AD: dbus_connection_send_with_reply (in /lib/x86_64-linux-gnu/libdbus-1.so.3.7.6)
==3832==    by 0x5388951: dbus_connection_send_with_reply_and_block (in /lib/x86_64-linux-gnu/libdbus-1.so.3.7.6)
==3832==    by 0x5384ADB: dbus_bus_register (in /lib/x86_64-linux-gnu/libdbus-1.so.3.7.6)
==3832==    by 0x5384D6E: internal_bus_get (in /lib/x86_64-linux-gnu/libdbus-1.so.3.7.6)
==3832==    by 0x40AF70: dbus_init (message_dbus.c:150)
==3832==    by 0x405818: main (tagfs.c:604)
==3832== 
==3832== LEAK SUMMARY:
==3832==    definitely lost: 184 bytes in 1 blocks
==3832==    indirectly lost: 383 bytes in 2 blocks
==3832==      possibly lost: 0 bytes in 0 blocks
==3832==    still reachable: 11,968 bytes in 78 blocks
==3832==         suppressed: 0 bytes in 0 blocks
==3832== Reachable blocks (those to which a pointer was found) are not shown.
==3832== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==3832== 
==3832== For counts of detected and suppressed errors, rerun with: -v
==3832== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)