gnome-shell crashed with SIGSEGV in crBufferPoolPush() [VBoxOGLcrutil.so]

[cputoaster]

virtualbox, upgrade from 17.04, ubuntu on xorg

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
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 23:30:38 2017
DisplayManager: lightdm
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2016-12-01 (322 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7f42c8795866 <crBufferPoolPush+54>: mov 0x8(%rbx),%rax
 PC (0x7f42c8795866) ok
 source "0x8(%rbx)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 crBufferPoolPush () from /usr/lib/x86_64-linux-gnu/VBoxOGLcrutil.so
 ?? () from /usr/lib/x86_64-linux-gnu/VBoxOGLcrutil.so
 ?? () from /usr/lib/x86_64-linux-gnu/VBoxOGLpackspu.so
 ?? () from /usr/lib/x86_64-linux-gnu/VBoxOGLpackspu.so
 ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-1.so
Title: gnome-shell crashed with SIGSEGV in crBufferPoolPush()
UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for perl-base
no debug symbol package found for perl-base
no debug symbol package found for liblttng-ust0

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!