gnome-shell crashed with SIGSEGV [Creating pipes for GWakeup: Too many open files]

[Jean-Baptiste Lallement]

Crashed when changing the volume with the keyboard's function keys.

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.10-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 14 15:41:10 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2014-07-15 (1430 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7f3548500351: rep movsq %ds:(%rsi),%es:(%rdi)
 PC (0x7f3548500351) ok
 source "%ds:(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%es:(%rdi)" (0x7f34c56fd7e0) ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_new () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_initable_new_valist () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_initable_new () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: Upgraded to cosmic on 2018-03-24 (81 days ago)
UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin lxd plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 _g_log_abort (breakpoint=1) at ../../../../glib/gmessages.c:583
 g_log_default_handler (log_domain=<optimized out>, log_level=<optimized out>, message=<optimized out>, unused_data=<optimized out>) at ../../../../glib/gmessages.c:3158
 default_log_handler (log_domain=log_domain@entry=0x7f355185c88e "GLib", log_level=log_level@entry=6, message=message@entry=0x7f34ac103520 "Creating pipes for GWakeup: Too many open files\n", data=data@entry=0x0) at ../src/main.c:310
 g_logv (log_domain=0x7f355185c88e "GLib", log_level=G_LOG_LEVEL_ERROR, format=<optimized out>, args=args@entry=0x7f34c56fe700) at ../../../../glib/gmessages.c:1370
 g_log (log_domain=log_domain@entry=0x7f355185c88e "GLib", log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x7f35518bd520 "Creating pipes for GWakeup: %s\n") at ../../../../glib/gmessages.c:1432

[Daniel van Vugt (vanvugt)]

jibel, it sounds like you might have a file descriptor leak, which is something I don't ever recall seeing in gnome-shell before.

If you can reproduce the issue in future then please try eliminating extensions:

b'org.gnome.shell' b'enabled-extensions' b"['<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>']"

[Daniel van Vugt (vanvugt)]

Or just keep an eye on the list of descriptors in:

/proc/PIDOFGNOMESHELL/fd/

and see if it grows with any duplicates.

[Launchpad Janitor (janitor)]

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

[Jean-Baptiste Lallement (jibel)]

For reference, this crash was caused by the system monitor extension. I disabled it and monitored over several days and the number of file descriptors is stable at 42.
Then I reenabled the extension and the number of file descriptors instantaneously started to grow over time.