Description of problem: Boxes crashed when the system was under memory load and an action (VM force shutdown) was requested from them. Version-Release number of selected component: gnome-boxes-3.8.3-1.fc19 Additional info: reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/bin/gnome-boxes crash_function: _mm_loadu_si128 executable: /usr/bin/gnome-boxes kernel: 3.9.4-300.fc19.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _mm_loadu_si128 at /usr/lib/gcc/x86_64-redhat-linux/4.8.0/include/emmintrin.h:684 #1 load_128_unaligned at pixman-sse2.c:370 #2 sse2_blt at pixman-sse2.c:4762 #4 sse2_composite_copy_area at pixman-sse2.c:4812 #5 pixman_image_composite32 at pixman.c:707 #6 _cairo_xlib_surface_draw_image at cairo-xlib-surface.c:1148 #7 surface_source at cairo-xlib-source.c:1012 #8 _cairo_xlib_source_create_for_pattern at cairo-xlib-source.c:1134 #9 composite_aligned_boxes at cairo-traps-compositor.c:1272 #10 clip_and_composite_boxes at cairo-traps-compositor.c:1766
Created attachment 756765 [details] File: backtrace
Created attachment 756766 [details] File: cgroup
Created attachment 756767 [details] File: core_backtrace
Created attachment 756768 [details] File: dso_list
Created attachment 756769 [details] File: environ
Created attachment 756770 [details] File: limits
Created attachment 756771 [details] File: maps
Created attachment 756772 [details] File: open_fds
Created attachment 756773 [details] File: proc_pid_status
Created attachment 756774 [details] File: var_log_messages
I clicked around to review VM settings during bootup. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: gnome-boxes crash_function: _mm_loadu_si128 executable: /usr/bin/gnome-boxes kernel: 3.9.8-300.fc19.x86_64 package: gnome-boxes-3.8.3-1.fc19 reason: Process /usr/bin/gnome-boxes was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000
(In reply to David Jaša from comment #0) > Description of problem: > Boxes crashed when the system was under memory load and an action (VM force > shutdown) was requested from them. I also hit this after clicking force shutdown.
Happened when I increased the amount of memory available to my VM, and clicked "attempt restart" when prompted to do so.
Running a Windows 7 virtual machine on my Fedora 19 system and attaching a USB Card Reader via the GNOME Boxes USB redirect feature. The Windows machine popped up a bubble in the lower right saying "The driver was not installed correctly" (or something similar, my Windows installation is German. The original Error message was "Der Treiber wurde nicht installiert"). Shortly after the CPU fan spun up and the GNOME Boxes UI crashed. The underlying qemu instance was not affected by this an the session could be reestablished by reopening Boxes. reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: gnome-boxes crash_function: _mm_loadu_si128 executable: /usr/bin/gnome-boxes kernel: 3.11.1-200.fc19.x86_64 package: gnome-boxes-3.8.4-2.fc19 reason: Process /usr/bin/gnome-boxes was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.