Bug 10226 - memory leak in libvirtd
Summary: memory leak in libvirtd
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2013-05-22 18:48 CEST by Renaud Michel
Modified: 2015-03-31 16:04 CEST (History)
3 users (show)

See Also:
Source RPM: libvirt-1.0.2-7.mga3.src.rpm
CVE:
Status comment:


Attachments
graph of libvirtd memory consumption (18.06 KB, image/png)
2013-05-22 18:51 CEST, Renaud Michel
Details

Description Renaud Michel 2013-05-22 18:48:00 CEST
Description of problem:
libvirtd memory consumption increase over time.

Version-Release number of selected component (if applicable):
First saw the problem with libvirt 1.0.2 from core/release.
I tried compiling the latest stable (1.0.5, the changelog mention some fixed memory leaks), but the problem is the same.

How reproducible:
After a restart of the libvirtd service, the libvirtd process will first use about 10MB RAM, than its memory will start increasing at approximatelly 2MB/hour.

Reproducible: 

Steps to Reproduce:
Comment 1 Renaud Michel 2013-05-22 18:51:24 CEST
Created attachment 4026 [details]
graph of libvirtd memory consumption

The first big rise which topped at 37MB was with libvirt 1.0.2
The second which is currently at 26 MB is with libvirt 1.0.5
Manuel Hiebel 2013-05-24 23:42:31 CEST

Keywords: (none) => Triaged
CC: (none) => alien, arnaud.patard, thierry.vignaud

Comment 2 Marja Van Waes 2015-03-31 16:04:11 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


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