gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()

[hackel]

This happens all the time. Multiple times per day. No idea what triggers it. Gnome-shell just randomly crashes. Thankfully I'm still running Xorg. I can't imagine switching to Wayland and having my entire session destroyed each time Gnome Shell crashes! I have no further information and cannot reproduce this with a particular action, but it happens at least once a a day now.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Oct 2 15:39:31 2017
DisplayManager: gdm3
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2014-08-03 (1155 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7fddb85a4e56 <g_type_check_instance_cast+22>: mov (%rdi),%rdi
 PC (0x7fddb85a4e56) ok
 source "(%rdi)" (0x00812cc8) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 g_type_check_instance_cast () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/gnome-shell/libgnome-shell.so
 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: Upgraded to artful on 2017-09-29 (3 days ago)
UserGroups: adm cdrom dip docker kvm libvirtd lpadmin lxd plugdev sambashare sudo video www-data

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1714745, so 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. Please continue to report any other bugs you may find.