gnome-shell crashed with SIGABRT in __GI_raise()

[Jack Peterson]

I was doing a project-wide find-and-replace in PHPStorm and the underlying java process probably consumed a metric crap-ton of RAM + CPU on my machine since the underlying files were a typical javascript dist file which weighs more than a neutron star. Ubuntu auto-recovered the desktop and I was able to continue my work -- so no harm, no foul... just glitchy.

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.30.0-3ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 3 10:37:08 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
 b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2018-03-28 (188 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
 __GI_abort () at abort.c:79
 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 meta_window_unmanage () from /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
Title: gnome-shell crashed with SIGABRT in __GI_raise()
UpgradeStatus: Upgraded to cosmic on 2018-10-01 (1 days ago)
UserGroups: adm cdrom dip docker kvm lpadmin 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 #1791574, 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.