Bug 1338042

Created attachment 1160060 [details]
File: backtrace

Created attachment 1160061 [details]
File: cgroup

Created attachment 1160062 [details]
File: core_backtrace

Created attachment 1160063 [details]
File: dso_list

Created attachment 1160064 [details]
File: environ

Created attachment 1160065 [details]
File: limits

Created attachment 1160066 [details]
File: maps

Created attachment 1160067 [details]
File: mountinfo

Created attachment 1160068 [details]
File: namespaces

Created attachment 1160069 [details]
File: open_fds

Created attachment 1160070 [details]
File: proc_pid_status

Created attachment 1160071 [details]
File: var_log_messages

Similar problem has been detected:

Crashy crashy, Boxes has been crashing randomly after long periods of time.

reporter:       libreport-2.7.0
backtrace_rating: 4
cmdline:        /usr/bin/gnome-boxes --gapplication-service
crash_function: g_thread_new
executable:     /usr/bin/gnome-boxes
global_pid:     5360
kernel:         4.5.4-300.fc24.x86_64
package:        gnome-boxes-3.20.2-1.fc24
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reason:         gnome-boxes killed by SIGTRAP
reproducible:   Not sure how to reproduce the problem
runlevel:       N 5
type:           CCpp
uid:            1000

I guess it must be leaking pthreads?

Similar problem has been detected:

Boxes crashes when left open for a long period of time.

reporter:       libreport-2.7.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-boxes --gapplication-service
crash_function: g_thread_new
executable:     /usr/bin/gnome-boxes
global_pid:     15195
kernel:         4.5.5-300.fc24.x86_64
package:        gnome-boxes-3.20.2-2.fc24
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reason:         gnome-boxes killed by SIGTRAP
reproducible:   Not sure how to reproduce the problem
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1350121 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

Was running in the background for hours.

reporter:       libreport-2.7.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-boxes --gapplication-service
crash_function: g_thread_new
executable:     /usr/bin/gnome-boxes
global_pid:     25246
kernel:         4.5.7-300.fc24.x86_64
package:        gnome-boxes-3.20.2-4.fc24
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reason:         gnome-boxes killed by SIGTRAP
reproducible:   Not sure how to reproduce the problem
runlevel:       N 5
type:           CCpp
uid:            1000

*** This bug has been marked as a duplicate of bug 1337007 ***

spice-gtk-0.32-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-de01d538f0

spice-gtk-0.32-2.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-de01d538f0

spice-gtk-0.32-2.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.

*** Bug 1358100 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

GNOME Boxes was running in the backgroudn with a Windows 10 guest. Guest had been mostly idle for about an hour.

reporter:       libreport-2.7.2
backtrace_rating: 4
cmdline:        gnome-boxes --open-uuid e02f011b-e334-4068-b285-7212870bea32
crash_function: g_thread_new
executable:     /usr/bin/gnome-boxes
global_pid:     6164
kernel:         4.6.4-301.fc24.x86_64
package:        gnome-boxes-3.20.2-4.fc24
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reason:         gnome-boxes killed by SIGTRAP
runlevel:       N 5
type:           CCpp
uid:            1000

Just hit this with spice-gtk3-0.32-2.fc24, reopening.

If you can catch this in gdb, I'd be interested in a 'thread apply all bt' (iow, wondering how many threads are there when this happens, and what they are doing).

(In reply to Christophe Fergeau from comment #25)
> If you can catch this in gdb, I'd be interested in a 'thread apply all bt'
> (iow, wondering how many threads are there when this happens, and what they
> are doing).

See comment #1, surprisingly looks like only seven threads.

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.