gnome-shell crashed with SIGABRT in __GI_raise()

[Azis naufal]

oazisn@wcjongkoks:~$ lsb_release -rd
Description: Ubuntu Groovy Gorilla (development branch)
Release: 20.10
oazisn@wcjongkoks:~$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.38.0-1ubuntu2
  Candidate: 3.38.0-1ubuntu2
  Version table:
 *** 3.38.0-1ubuntu2 500
        500 http://id.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
        100 /var/lib/dpkg/status
oazisn@wcjongkoks:~$

Honestly, I don't really know what happen. I was switch to ubuntu on wayland and open google chrome and everything freeze. I think gnome-shell is crashing. So it return tu gdm login screen.

ProblemType: Crash
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
Uname: Linux 5.8.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu49
Architecture: amd64
CasperMD5CheckResult: skip
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 6 11:53:04 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2020-10-06 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201004)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
 __GI_abort () at abort.c:79
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/gnome-shell/libst-1.0.so
Title: gnome-shell crashed with SIGABRT in __GI_raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

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