Gnome Shell crashes with SIGSEGV when Android emulator started

[Kostadin Stoilov]

I am filing this bug with gjs because the behaviour started after upgrading to 1.52.5-0ubuntu18.04.1

Steps to reproduce are:

1. Launch an Android emulator from Android Studio: I used all default settings and Andoid Pie x86 image

2. Change workspace via hotkey

3. Result is gnome-shell crashes and resets

Workaround is to run:
sudo apt install libgjs0g=1.52.1-1ubuntu1
sudo apt install gjs=1.52.1-1ubuntu1

This is from /var/log/syslog at the time of the gnome-shell crash

Jan 22 06:01:10 kostadin-XPS gnome-shell[16305]: value "-1,000000" of type 'gfloat' is invalid or out of range for property 'width' of type 'gfloat'
Jan 22 06:01:10 kostadin-XPS gnome-shell[16305]: value "-1,000000" of type 'gfloat' is invalid or out of range for property 'height' of type 'gfloat'
Jan 22 06:01:10 kostadin-XPS gnome-shell[16305]: value "-1,000000" of type 'gfloat' is invalid or out of range for property 'width' of type 'gfloat'
Jan 22 06:01:10 kostadin-XPS gnome-shell[16305]: value "-1,000000" of type 'gfloat' is invalid or out of range for property 'height' of type 'gfloat'
Jan 22 06:01:13 kostadin-XPS gnome-shell[16305]: Object Gio.Settings (0x55703194e880), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
Jan 22 06:01:13 kostadin-XPS gnome-shell[16305]: g_object_run_dispose: assertion 'G_IS_OBJECT (object)' failed
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: == Stack trace for context 0x55702bd7d340 ==
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #0 0x55702c135080 i resource:///org/gnome/shell/ui/messageTray.js:173 (0x7f5560090ab0 @ 22)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #1 0x7ffc05c1e680 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5542db5de0 @ 71)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #2 0x55702c134fe0 i resource:///org/gnome/shell/ui/messageTray.js:812 (0x7f55600a0098 @ 28)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #3 0x7ffc05c1f260 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5542db5de0 @ 71)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #4 0x55702c134f40 i resource:///org/gnome/shell/ui/windowAttentionHandler.js:100 (0x7f5542c43808 @ 42)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #5 0x7ffc05c1fe40 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5542db5de0 @ 71)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #6 0x55702c134ec8 i resource:///org/gnome/shell/ui/windowAttentionHandler.js:44 (0x7f5542c43340 @ 17)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #7 0x7ffc05c21150 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f5542dd2230 @ 386)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #8 0x55702c134e40 i resource:///org/gnome/shell/ui/messageTray.js:479 (0x7f556009db38 @ 22)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #9 0x7ffc05c21da0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5542db5de0 @ 71)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #10 0x55702c134dc0 i resource:///org/gnome/shell/ui/calendar.js:801 (0x7f55600a9ef0 @ 22)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #11 0x7ffc05c22990 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5542db5de0 @ 71)
Jan 22 06:01:13 kostadin-XPS org.gnome.Shell.desktop[16305]: #12 0x7ffc05c22a60 b self-hosted:918 (0x7f5542df12b8 @ 394)
Jan 22 06:01:55 kostadin-XPS gnome-shell[16305]: Object Meta.WindowActor (0x55702f200b80), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: == Stack trace for context 0x55702bd7d340 ==
Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #0 0x55702c134e48 i resource:///org/gnome/shell/ui/windowManager.js:1787 (0x7f5542b24670 @ 113)
Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #1 0x7ffc05c21040 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5542db5de0 @ 71)
Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #2 0x55702c134dc0 i resource:///org/gnome/shell/ui/tweener.js:112 (0x7f5542dc8e68 @ 37)
Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #3 0x7ffc05c22ab0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7f5542dd2b38 @ 54)
Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #4 0x7ffc05c22c00 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7f5542dd2bc0 @ 1626)
Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #5 0x7ffc05c22cb0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f5542dd2c48 @ 100)
Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #6 0x7ffc05c22d40 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f5542dd2cd0 @ 10)
Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #7 0x7ffc05c22e30 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f5542dd2230 @ 386)
Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #8 0x7ffc05c22ee0 b resource:///org/gnome/shell/ui/tweener.js:244 (0x7f5542dcf808 @ 159)
Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #9 0x7ffc05c22f40 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f5542db5de0 @ 71)
Jan 22 06:01:55 kostadin-XPS org.gnome.Shell.desktop[16305]: #10 0x7ffc05c22fe0 b resource:///org/gnome/shell/ui/tweener.js:219 (0x7f5542dcf780 @ 15)
Jan 22 06:01:55 kostadin-XPS kernel: [153510.297083] gnome-shell[16305]: segfault at 28 ip 00007f5588f3efe0 sp 00007ffc05c20088 error 4 in libmutter-2.so.0.0.0[7f5588ebb000+157000]
Jan 22 06:01:55 kostadin-XPS gnome-session[16194]: gnome-session-binary[16194]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gjs 1.52.5-0ubuntu18.04.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 22 05:59:31 2019
InstallationDate: Installed on 2016-04-29 (997 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gjs
UpgradeStatus: Upgraded to bionic on 2018-08-04 (170 days ago)

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Daniel van Vugt (vanvugt)]

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

[Stephan Henningsen (zta77)]

This is really getting a big problem since I cannot use the emulator for my daily work.

Is there anything I can do to help debug this?

It is quite easy to reproduce as it happens every time I switch workspace with the emulator running, no matter what state the emulator is in; meaning the developers of this can easily reproduce this themselves:

1) Install full Android Studio with JDK, e.g. in ~/opt/android-studio to not pollute their computer
2) Start the Emulator; install any Android version in the process.
3) Switch Workspace.
4) Observe crash.

[Stephan Henningsen (zta77)]

I see this bug has been marked as a duplicate; ignore my post, sorry.