We would really need some sort of reproduce to set MALLOC_CHECK_ and rerun or into valgrind.
But it doesn't show in any of the libvirt tests that we run regular and often so it seems to be either really randomly or related to some yet unclear special config/HW. Normally this would be "invalid" but that doesn't make much sense on a bug reported by just passing the threshold of being too often to be ignored. This is on the backlog but lower prio than it should be due to the unclarity how to proceed without and repro cahnce. Really, if anybody encounters a repro chance on that please update the bug here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577613 Title: /usr/sbin/libvirtd:*** Error in `/usr/sbin/libvirtd': malloc(): memory corruption: ADDR *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1577613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
