Bug 882148

Summary:	virt-manager with no running VMs consumes huge amounts of memory
Product:	[Fedora] Fedora	Reporter:	Honza Horak <hhorak>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	berrange, crobinso, hbrock, herrold, jforbes, virt-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-06-12 19:37:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Honza Horak 2012-11-30 09:30:14 UTC

Description of problem:
I've had virt-manager running for few days (including suspending) and did approx. 10 actions like start/stop VM (VM were RHEL-5, RHEL-6, Fedora). Finally there is no running VM, but virtual-manager still consumes a huge amounts of memory and even consumes quite a lot processor time:

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
hhorak    8151  3.8 16.0 1567028 617416 ?      Ssl  Nov27 166:06 python /usr/share/virt-manager/virt-manager.py

Version-Release number of selected component (if applicable):
virt-manager-0.9.4-3.fc18.noarch

How reproducible:
usually after several days of running

Steps to Reproduce:
1. work with virt-manager few days (start/stop VMs)
2. do some suspends
3. see virt-manager's consumed memory
  
Actual results:
virt-manager consumes over 500MB when no VM is running any more

Expected results:
virt-manager consumes say 50MB, like when it is fresh started

Comment 1 Cole Robinson 2013-06-12 19:37:46 UTC


*** This bug has been marked as a duplicate of bug 972371 ***