gnome-shell crashed with SIGSEGV

[Jean-Baptiste Lallement]

(Tested under wayland)

Test Case:
1. Launch gnome-boxes
2. Create a new VM of Ubuntu Artful and run it
3. Go the the live session in the VM
4. Close gnome-boxes but keep the VM running
5. Launch gnome-boxes again

Expected result
gnome-boxes is reattached to the VM

Actual result
This crash

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 25 16:15:11 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2013-09-03 (1482 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f9d310fc4af: mov 0x8(%rdi),%eax
 PC (0x7f9d310fc4af) ok
 source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so
 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so
 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 () at /usr/lib/libgjs.so.0
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev sambashare sudo

[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 #1715330, 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.