Was sorting a 15 MB libreoffice-calc spreadsheet when a freeze appeared (many other sorts were made previously to that one), then get that crash.
I've observed many times a similar freeze (with gnome-shell 3.22 too), usually a short one, but blaming some buffer/array ram botleneck: cant say if its a gnome-shell/kernel/else problem, but many times the swap partition is progressively used ( 3 -> 40% ) and that one is never fully freed when all apps are closed and the system is idled for a long time (seems unexpected).
ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: gnome-shell 3.23.90-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
Uname: Linux 4.10.0-8-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Feb 20 10:11:47 2017
DisplayManager: lightdm
ExecutablePath: /usr/bin/gnome-shell
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f138f144f85: testb $0x1,(%rax)
PC (0x7f138f144f85) ok
source "$0x1" ok
destination "(%rax)" (0x7f133f0fffe8) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
?? () from /usr/lib/libgjs.so.0
g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
meta_run () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0
Title: gnome-shell crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev sambashare sudo users
Thank you for taking the time to report this bug and helping to make Ubuntu better.
However, processing it in order to get sufficient information for the developers failed (it does not generate an useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report. Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report.
Thank you for your understanding, and sorry for the inconvenience!