Public bug reported:
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.
** Affects: libvirt (Ubuntu)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Affects: libvirt (Ubuntu Xenial)
Importance: Undecided
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: New
** Tags: sts
** Also affects: libvirt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Xenial)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
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
