Red Hat Bugzilla – Bug 1000738
remote-viewer application error exception 0x40000015
Last modified: 2016-01-06 06:07:03 EST
Created attachment 789901 [details]
event log entry
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
Nothing specific. Used long enough remote-viewer crashes.
Steps to Reproduce:
Windows host details
Windows 7 Enterprise SP1 6.1.7601 x64
Linux host details
Fedora 19 x86_64, 3.10.9
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
Created attachment 790002 [details]
Created attachment 790003 [details]
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.
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
This is still happening with version 0.6.0. Both x32 and x64.
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:
Guess we should pull this fix in the mingw-gtk2 package even if it does not make it upstream...
I support this idea too. The bugfix exists since 11 months and did not find its way into gtk2. Several people reported that the fix works. For running virt-viewer in 16bbp this bugfix is nearly essential.
*** Bug 1062749 has been marked as a duplicate of this bug. ***
The fix is in, and in the latest release gtk3 is used