** Summary changed:
- Memory leak on libvirt 1.3.1
+ Memory leak of struct _virPCIDeviceAddress on libvirt
** Changed in: libvirt (Ubuntu Focal)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1844455
Title:
Memory leak of struct _virPCIDeviceAddress on libvirt
Status in Ubuntu Cloud Archive:
Confirmed
Status in Ubuntu Cloud Archive mitaka series:
Confirmed
Status in libvirt package in Ubuntu:
Fix Released
Status in libvirt source package in Xenial:
Confirmed
Status in libvirt source package in Bionic:
Confirmed
Status in libvirt source package in Eoan:
Confirmed
Status in libvirt source package in Focal:
Fix Released
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
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
