[regression] gnome-shell crashed with SIGTRAP in g_realloc_n() from g_log_structured()

[Maciej Borzecki]

https://errors.ubuntu.com/problem/bf61cf0ebedaacbd48f7c12574f551fea3f706c7
https://errors.ubuntu.com/problem/bc2bd5031309e8cf2314785805634f998452e937
https://errors.ubuntu.com/problem/f30049f514bf17053fe0461bf2b0890e46ad32dd

---

Freshly installed bionic.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Thu Mar 22 12:22:58 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2018-03-22 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321)
ProcCmdline: /usr/bin/gnome-shell
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 g_realloc_n () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_structured () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
Title: gnome-shell crashed with signal 5 in g_realloc_n()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 g_realloc_n () from /tmp/apport_sandbox_d15w8xzz/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_structured () from /tmp/apport_sandbox_d15w8xzz/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /tmp/apport_sandbox_d15w8xzz/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /tmp/apport_sandbox_d15w8xzz/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel van Vugt (vanvugt)]

No reports of this new crash on errors.ubuntu.com yet, but I think we can expect to see it there soon.

[Brian Murray (brian-murray)]

There is a bit of a backlog which the errors.ubuntu.com retracers are working through so it could be a while.

[Daniel van Vugt (vanvugt)]

This looks like maybe a regression in this (which was published the day before the first crash report):

https://launchpad.net/ubuntu/+source/glib2.0/2.56.0-2ubuntu1

[Daniel van Vugt (vanvugt)]

It looks like these (including the #1 gnome-shell crash in 18.04 this week) but the lack of debug symbols is a problem:

https://errors.ubuntu.com/problem/bf61cf0ebedaacbd48f7c12574f551fea3f706c7
https://errors.ubuntu.com/problem/bc2bd5031309e8cf2314785805634f998452e937
https://errors.ubuntu.com/problem/f30049f514bf17053fe0461bf2b0890e46ad32dd

[Marco Trevisan (Treviño) (3v1n0)]

I think this is just a false-positive, as we're probably crashing before or aborting but then we fail at the point we try to get the gjs stack.

So, probably we should get journalctl from such crashes to see if any JS calltrace is there.

[Daniel van Vugt (vanvugt)]

That sounds plausible.

Also there are zero reports of this crash after gnome-shell 3.28.0. So zero crashes in Ubuntu 18.10, and zero crashes since the final release of Ubuntu 18.04.

The only systems still crashing seem to be pre-release bionic systems that haven't been updated for most of the year.

I think this looks fixed already. Maybe fixed as early as the final release of 18.04.