Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Cause:
Resizing remote display resolution.
Consequence:
Large memory leak.
Fix:
Remove the memory leak when resizing guest resolution.
Result:
Remote display can be resized without memory leak.
DescriptionMarian Krcmarik
2012-03-21 17:51:49 UTC
Created attachment 571798[details]
/var/log/messages
Description of problem:
Memory leaks happen when resizing resolution on guest or scaling remote-viewer client. When running a hundreds of quick resolutions changes The resident memory of client process seems to be stable but cache memory is all eaten up to the top of available memory and then whole swap is eaten as well which results in crash of client system (possible see the attached output from messages).
Version-Release number of selected component (if applicable):
Client is RHEL6.3, Guest fedora or Windows7
spice-gtk-0.11-1.el6.x86_64
spice-glib-0.11-1.el6.x86_64
spice-gtk-tools-0.11-1.el6.x86_64
spice-gtk-python-0.11-1.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Connect with remote-viewer to a guest.
2. If the guest is Linux run something like:
for ((i=0;$i<2000;i++)); do echo ${i}; if [ "x$((i%3))" == "x0" ]; then MODE="1280x800"; elif [ "x$((i%3))" == "x1" ]; then MODE="1440x900"; else MODE="1680x1050"; fi ; xrandr --output default --mode "${MODE}" 2> /dev/null; sleep 0.3333333; done
OR
If guest is Windows use tool i.e nircmd utility to change resolution in a loop (www.nirsoft.net/utils/nircmd.html)
Actual results:
cache memory and swap starts to dramatically get high which results to remote-viewer or system crash
Expected results:
Stable memory results
Additional info:
Comment 2Marc-Andre Lureau
2012-03-22 13:27:06 UTC
Comment 8Marc-Andre Lureau
2012-04-20 13:22:40 UTC
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
No documentation needed.
Comment 9Marc-Andre Lureau
2012-04-20 13:42:38 UTC
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1,11 @@
-No documentation needed.+Cause:
+Resizing remote display resolution.
+
+Consequence:
+Large memory leak.
+
+Fix:
+Remove the memory leak when resizing guest resolution.
+
+Result:
+Remote display can be resized without memory leak.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2012-0767.html
Created attachment 571798 [details] /var/log/messages Description of problem: Memory leaks happen when resizing resolution on guest or scaling remote-viewer client. When running a hundreds of quick resolutions changes The resident memory of client process seems to be stable but cache memory is all eaten up to the top of available memory and then whole swap is eaten as well which results in crash of client system (possible see the attached output from messages). Version-Release number of selected component (if applicable): Client is RHEL6.3, Guest fedora or Windows7 spice-gtk-0.11-1.el6.x86_64 spice-glib-0.11-1.el6.x86_64 spice-gtk-tools-0.11-1.el6.x86_64 spice-gtk-python-0.11-1.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Connect with remote-viewer to a guest. 2. If the guest is Linux run something like: for ((i=0;$i<2000;i++)); do echo ${i}; if [ "x$((i%3))" == "x0" ]; then MODE="1280x800"; elif [ "x$((i%3))" == "x1" ]; then MODE="1440x900"; else MODE="1680x1050"; fi ; xrandr --output default --mode "${MODE}" 2> /dev/null; sleep 0.3333333; done OR If guest is Windows use tool i.e nircmd utility to change resolution in a loop (www.nirsoft.net/utils/nircmd.html) Actual results: cache memory and swap starts to dramatically get high which results to remote-viewer or system crash Expected results: Stable memory results Additional info: