Bug 1411250 - some objects leaked logs are printed when connecting virt-manager by ssh
Summary: some objects leaked logs are printed when connecting virt-manager by ssh
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Pavel Hrdina
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-09 09:12 UTC by Xiaodai Wang
Modified: 2017-03-02 19:34 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-02 19:34:23 UTC
Target Upstream Version:


Attachments (Terms of Use)
virt-manager debug logs (14.62 KB, text/plain)
2017-01-09 09:13 UTC, Xiaodai Wang
no flags Details
guest xml (2.97 KB, text/plain)
2017-01-09 09:13 UTC, Xiaodai Wang
no flags Details

Description Xiaodai Wang 2017-01-09 09:12:25 UTC
Description of problem:
some objects leaked logs are printed when connecting virt-manager by ssh

Version-Release number of selected component (if applicable):
virt-manager-0.9.0-33.el6.x86_64

How reproducible:
100%

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.

Actual results:
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)>

Expected results:
No leaked logs should be printed.

Additional info:
RHEL7 doesn't have this problem.

Comment 1 Xiaodai Wang 2017-01-09 09:13:17 UTC
Created attachment 1238589 [details]
virt-manager debug logs

Comment 2 Xiaodai Wang 2017-01-09 09:13:53 UTC
Created attachment 1238590 [details]
guest xml

Comment 6 Cole Robinson 2017-03-02 19:34:23 UTC
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

Comment 7 Cole Robinson 2017-03-02 19:34:58 UTC
err that should have said RHEL6, but the same logic would apply to similar issues in RHEL7 too :)


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