Created attachment 827837 [details] Xorg log file from X terminating Description of problem: We have virtualization hosts running qemu-kvm 1.1.2 with spice 0.12.2. Those hosts run Fedora16 VMs very well. When we create Fedora 19 instances, we've found that after 1-5 days of usage, Xorg will terminate unexpectedly on the user reporting out of memory. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a Fedora 19 VM on one of our virtualization hosts 2. Log in (we generally use KDE, XFCE, or MATE) 3. Use the VM for a few days for normal use. Actual results: After 1-5 days depending on desktop usage, X terminates with an out of memory issue such as: [1024592.839] Out of memory allocating 261140 bytes [1024592.839] Out of mem - stats [1024592.850] max system bytes = 243257344 [1024592.850] system bytes = 243257344 [1024592.850] in use bytes = 133245384 Expected results: X should continue running indefinitely (as it does on e.g. Fedora 16) Additional info: Sample Xorg log file attached
Created attachment 828710 [details] Another Xorg log file, this time with backtraces This crash just occurred this morning. The log file includes some backtraces. This log file is from using xorg-x11-drv-qxl-0.1.1-2.fc19.x86_64
Created attachment 829440 [details] valgrind output from a short run of Xspice Valgrind definitely sees leaks in the qxl driver.
Have same problem from F19->F20 last qxl driver : xorg-x11-drv-qxl-0.1.1-4.fc20.x86_64 Option "EnableSurfaces" "False" - in xorg.conf
i noticed that problem appears when you set "nomodeset" in kernel string parameters.
We are still seeing this problem with F21 guests.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
A few more details would help. First, if you can install debug symbols for the spice driver package, the backtrace and valgrind logs should be a bit more useful. Second, does the memory usage of the spice server grow across the 4 days? Your backtrace shows some evidence of a process running out of control (not clearing the event queue), so it may not be a leak so much as something nasty that happens after a period of time. Third, it would be helpful with valgrind if you could first valgrind a short session (and check to see if debug info is now giving line numbers). Then valgrind a long session; a day perhaps. The difference between those two will then be very interesting and may provide a clue. Cheers, Jeremy
Could be http://cgit.freedesktop.org/xorg/driver/xf86-video-qxl/commit/?id=3d511c30206bd8c9a207 or http://cgit.freedesktop.org/xorg/driver/xf86-video-qxl/commit/?id=2bed9bffd92a1422a460dad37e5fffe820ef2df3 f21 scratch build with these patches at http://koji.fedoraproject.org/koji/taskinfo?taskID=9807280 if you want to give them a try.
I work with Nahum, and I've been testing the scratch build Christophe Fergeau linked to since 05/20. It does seem to resolve the problem for us, though this bug has been difficult to reliably replicate.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.