Bug 528162 - Fix memory leak in libvirtd in F12
Summary: Fix memory leak in libvirtd in F12
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: rawhide
Hardware: All
OS: Linux
high
medium
Target Milestone: ---
Assignee: Mark McLoughlin
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F12VirtBlocker
TreeView+ depends on / blocked
 
Reported: 2009-10-09 13:40 UTC by Richard W.M. Jones
Modified: 2009-10-12 08:58 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-12 07:16:12 UTC


Attachments (Terms of Use)

Description Richard W.M. Jones 2009-10-09 13:40:27 UTC
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:

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
http://libvirt.org/git/?p=libvirt.git;a=commit;h=c6f1459eb998619ab21a92d9bb87341f26978181

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

libvirt-0.7.1-10.fc12.x86_64

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 14:56:23 UTC
* 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 16:01:28 UTC
tag request: https://fedorahosted.org/rel-eng/ticket/2429

Comment 3 Mark McLoughlin 2009-10-12 07:16:12 UTC
tagged now for F12 GA

Comment 4 Richard W.M. Jones 2009-10-12 08:58:20 UTC
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.