Bug 528162 - Fix memory leak in libvirtd in F12
Fix memory leak in libvirtd in F12
Product: Fedora
Classification: Fedora
Component: libvirt (Show other bugs)
All Linux
high Severity medium
: ---
: ---
Assigned To: Mark McLoughlin
Fedora Extras Quality Assurance
Depends On:
Blocks: F12VirtBlocker
  Show dependency treegraph
Reported: 2009-10-09 09:40 EDT by Richard W.M. Jones
Modified: 2009-10-12 04:58 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-10-12 03:16:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Richard W.M. Jones 2009-10-09 09:40:27 EDT
Description of problem:

libvirtd in F12 leaks pretty bad when you make invalid
requests against the daemon.  For example, try doing

  # virsh dominfo 0

in a loop on a machine running qemu/kvm hypervisor.

Dan tells me that this is fixed by the following upstream

commit c6f1459eb998619ab21a92d9bb87341f26978181
Author: Matthias Bolte <matthias.bolte@googlemail.com>
Date:   Wed Sep 30 02:17:27 2009 +0200
     Fix memory leaks in libvirtd's message processing

Version-Release number of selected component (if applicable):


How reproducible:

Run this command as root several times, or in a loop:

  virsh dominfo 0

Check the output of 'top' to see libvirtd growing in size.
Comment 1 Mark McLoughlin 2009-10-09 10:56:23 EDT
* Fri Oct  9 2009 Mark McLoughlin <markmc@redhat.com> - 0.7.1-11
- Fix libvirtd memory leak during error reply sending (#528162)
- Add several PCI hot-unplug typo fixes from upstream
Comment 2 Mark McLoughlin 2009-10-09 12:01:28 EDT
tag request: https://fedorahosted.org/rel-eng/ticket/2429
Comment 3 Mark McLoughlin 2009-10-12 03:16:12 EDT
tagged now for F12 GA
Comment 4 Richard W.M. Jones 2009-10-12 04:58:20 EDT
I've confirmed that the -11 package fixes the bug I was seeing.

Note You need to log in before you can comment on or make changes to this bug.