Hide Forgot
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:
Fixed upstream commit 6db275a422013a34247b805923f88b23db850ea1 Author: Marc-André Lureau <marcandre.lureau> Date: Wed Mar 21 19:18:38 2012 +0100 Always release shm of primary surfaces Always remove shared memory segment of primary surfaces when destroying its canvas.
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.
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