[Bug 1844455] Re: Memory leak on libvirt 1.3.1

[Guilherme G. Piccoli]

Hi Christian, thanks for your comment! I didn't receive an email with that comment, unfortunately.
I'm not sure if they happen on upstream version, I've tried already and saw different leaks, potentially correlated with the virErr ones.

I couldn't see libxml2 leaks. But i continue the investigation, thanks!

-- 
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