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
*** This bug has been marked as a duplicate of bug 972371 ***