Would be nice to get the patch from https://bugzilla.gnome.org/show_bug.cgi?id=671538#c15 in the mingw-gtk2 package as this can be hit with mingw-remote-viewer which is built using mingw-gtk2 from fedora. +++ This bug was initially created as a clone of Bug #1000738 +++ Description of problem: remote-viewer randomly crashes when using Windows x64 package Version-Release number of selected component (if applicable): 0.5.7 x64 build How reproducible: Nothing specific. Used long enough remote-viewer crashes. Steps to Reproduce: 1. None Actual results: Expected results: Additional info: Windows host details Windows 7 Enterprise SP1 6.1.7601 x64 Linux host details Fedora 19 x86_64, 3.10.9 libvirt 1.0.5.5-1 qemu-kvm 1.4.2-7 virt-manager 0.10.0-1 Using QXL/spice, latest spice guest tools installed in Windows guest (0.59) Local virt-manager session does not crash remote-viewer session running on Linux to same VM does not crash --- Additional comment from on 2013-08-25 00:59:29 EDT --- --- Additional comment from on 2013-08-25 01:09:47 EDT --- --- Additional comment from on 2013-08-25 01:12:20 EDT --- After further investigation, there appears appears to be a memory leak which is why the crash is random. remote-viewer process will get to approx. 500MB and then crash. --- Additional comment from Benjamin Reiter on 2013-12-12 10:00:05 EST --- I can confirm this bug. Remote-Viewer.exe crashes after a while due to high memory consumption. Easily reproducible by opening the theme selection on a Windows 7 guest and cycling between the themes "Windows 7" and "Windows Classic". Is there a workaround or fix available? Guest-OS is Windows 7 x64 Remote-Viewer Client x64 on OS Windows 7 x64 --- Additional comment from Benjamin Reiter on 2014-02-03 13:30:32 EST --- This is still happening with version 0.6.0. Both x32 and x64. --- Additional comment from Markus Stockhausen on 2014-02-09 12:17:52 EST --- VNC sessions seem to be affected by this bug too. The easiest way I could reproduce the bug was opening a window in the windows VM. Afterwards just click on the taskbar icon to open/close the window cyclically. It takes only a minute to raise the crash. Most important: In my environment the bug shows up only when using 16bpp depth on the client. So at least one part of the problem should be this: https://bugzilla.gnome.org/show_bug.cgi?id=671538 --- Additional comment from Christophe Fergeau on 2014-02-11 04:23:24 EST --- Guess we should pull this fix in the mingw-gtk2 package even if it does not make it upstream...
mingw-gtk2-2.24.22-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mingw-gtk2-2.24.22-2.fc19
mingw-gtk2-2.24.22-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/mingw-gtk2-2.24.22-2.fc20
Just downloaded the packages and built a new virt-viewer package. RAM utilization is back to normal in 16bpp.
Package mingw-gtk2-2.24.22-2.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mingw-gtk2-2.24.22-2.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-2374/mingw-gtk2-2.24.22-2.fc20 then log in and leave karma (feedback).
mingw-gtk2-2.24.22-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
mingw-gtk2-2.24.22-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.