[Bug 1844455] Re: Memory leak on libvirt 1.3.1

[Guilherme G. Piccoli]

We validated that commit 38816336a5 ("node_device_conf: Don't leak
@physical_function in virNodeDeviceGetPCISRIOVCaps") [0] indeed fixes
the leak investigated. Although there are more definitely-lost memory
reports from Valgrind, they are ultimately glibc-related and given the
report was in Trusty and they are not considerable leaks (at most,
8K/24H) our focus will be to fix the PCI-related leak in all libvirt
releases.

SRU template and debdiffs will get added here soon.
Cheers,


Guilherme


[0] libvirt.org/git/?p=libvirt.git;a=commit;h=38816336a5

** Also affects: libvirt (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Also affects: libvirt (Ubuntu Focal)
   Importance: High
     Assignee: Guilherme G. Piccoli (gpiccoli)
       Status: Confirmed

** Also affects: libvirt (Ubuntu Eoan)
   Importance: Undecided
       Status: New

** Changed in: libvirt (Ubuntu Eoan)
       Status: New => Confirmed

** Changed in: libvirt (Ubuntu Bionic)
       Status: New => Confirmed

** Changed in: libvirt (Ubuntu Xenial)
       Status: New => Confirmed

** Changed in: libvirt (Ubuntu Eoan)
   Importance: Undecided => High

** Changed in: libvirt (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: libvirt (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: libvirt (Ubuntu Bionic)
     Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Changed in: libvirt (Ubuntu Eoan)
     Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

-- 
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:
  Confirmed
Status in libvirt source package in Bionic:
  Confirmed
Status in libvirt source package in Eoan:
  Confirmed
Status in libvirt source package in Focal:
  Confirmed

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