[Bug 1844455] Re: Memory leak on libvirt 1.3.1

[Christian Ehrhardt ]

Hi,
thanks for the report and your work on it.
Are you sure those issues are not happening on newer versions?

Because
a) if they are fixed in newer versions then I'd ask you to backport the respective fixes from there (can be partial if they were bigger reworks, but always better than starting from scratch).
b) if they are not fixed in newer versions we should address and fix those as well (For SRU policy and long term viability)

So after your further analysis of the case give the new versions a check
in that regard please.

-- 
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:
  New
Status in Ubuntu Cloud Archive mitaka series:
  New
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