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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844455 Title: Memory leak on libvirt 1.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1844455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
