/usr/sbin/libvirtd:*** Error in `/usr/sbin/libvirtd': malloc(): memory corruption: ADDR ***

[errors.ubuntu.com bug bridge]

The Ubuntu Error Tracker has been receiving reports about a problem regarding libvirt. This problem was most recently seen with version 1.3.1-1ubuntu10, the problem page at https://errors.ubuntu.com/problem/e830535a29f957db6735f9dcd95a0eb8822f98ad contains more details.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Dongwon Cho (dongwoncho)]

It affects me as well.
https://paste.ubuntu.com/23418809/

[Christian Ehrhardt  (paelzer)]

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.

[Launchpad Janitor (janitor)]

[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.]