Description of problem:
some objects leaked logs are printed when connecting virt-manager by ssh
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. login a remote guest by ssh with '-X'.
2. Open virt-manager by 'virt-manager --debug'.
3. Double click a guest, start it, and then force off it.
4. Close the vm window and virt-manager window.
5. Check the virt-manager debugging logs.
some object leaked logs are printed.
2017-01-09 16:59:24,553 (engine:549): Leaked <vmmDomain object at 0x2a63a50 (virtManager+domain+vmmDomain at 0x2823080)>
2017-01-09 16:59:24,553 (engine:549): Leaked <vmmConsolePages object at 0x2a90780 (virtManager+console+vmmConsolePages at 0x316e580)>
2017-01-09 16:59:24,553 (engine:549): Leaked <SpiceViewer object at 0x3214aa0 (GObject at 0x336d340)>
No leaked logs should be printed.
RHEL7 doesn't have this problem.
Created attachment 1238589 [details]
virt-manager debug logs
Created attachment 1238590 [details]
These messages are basically harmless. Leaked objects over time can cause memory usage to balloon, but that's only with heavy app interactivity. They are in the --debug log for a reason, and infact upstream they are disabled by default, it's just a handy tool to help find circular references with the UI objects
So IMO this is WONTFIX for RHEL7 unless it's creating an actual problem
err that should have said RHEL6, but the same logic would apply to similar issues in RHEL7 too :)