[Bug 1844455] Re: Memory leak on libvirt 1.3.1
Guilherme G. Piccoli
1844455 at bugs.launchpad.net
Tue Dec 3 11:36:17 UTC 2019
Just a minor update here, we found one leak to be fixed by the following commit:
libvirt.org/git/?p=libvirt.git;a=commit;h=38816336a5 .
We continue the investigation of the other leaks.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1844455
Title:
Memory leak on libvirt 1.3.1
Status in Ubuntu Cloud Archive:
Confirmed
Status in Ubuntu Cloud Archive mitaka series:
Confirmed
Status in libvirt package in Ubuntu:
Confirmed
Status in libvirt source package in Xenial:
New
Bug description:
It was reported that libvirt 1.3.1 running on Trusty (through
UCA/Mitaka) is getting OOM'ed after a while - in our reports took 2
years for the leak to trigger an out-of-memory situation, but this may
change according to the user available memory.
Valgrind was executed in a similar environment, we were able to
collect information about the "definitely lost" memory of libvirt
process (attached) below.
The leaks are detailed in next comments.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1844455/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list