gnome-shell crashed with signal 5 in _XIOError()

[Nathaniel Simard]

When I work with a lot of stuff open like chrome, vscode a terminal then it crashes often when switching tabs in chrome or even Firefox. If I'm under Wayland with Intel graphic, the hole session is lost and I go back to the login screen. So I have to stay in X because gnome can be restarted and I don't lose everything.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sun Oct 22 20:17:53 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2017-10-19 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/gnome-shell
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-shell crashed with signal 5 in _XIOError()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 x_io_error (display=<optimized out>) at wayland/meta-xwayland.c:411
 _XIOError (dpy=dpy@entry=0x5617cbe64ca0) at ../../src/XlibInt.c:1469
 _XEventsQueued (dpy=dpy@entry=0x5617cbe64ca0, mode=mode@entry=2) at ../../src/xcb_io.c:352
 XPending (dpy=0x5617cbe64ca0) at ../../src/Pending.c:55
 gdk_check_xpending (display=0x5617cbe75060) at ././gdk/x11/gdkeventsource.c:269

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1505409, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.