Comment 3 for bug 1844455

Leak #2:

==21823== 385 (280 direct, 105 indirect) bytes in 1 blocks are definitely lost in loss record 88 of 106
==21823== at 0x4C2CC70: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==21823== by 0x50A5299: virAlloc (viralloc.c:144)
==21823== by 0x14B185: daemonConfigNew (libvirtd-config.c:242)

This one is similar to the previous one, it's likely struct daemonConfig is leaked.
This structure is allocated in daemonNew and freed by daemonConfigFree(), at the end
of libvirtd main() function. The hypothesis here again is that we had either a process
killed or we should correctly terminate Valgrind in order it collects the free
calls for this object.