gjs-console crashed with SIGSEGV in g_socket_receive_message_with_timeout()

[El jinete sin cabeza]

https://errors.ubuntu.com/problem/434b8b4abd971c7f84ca824ef5878a00d547753a
https://gitlab.gnome.org/GNOME/gjs/issues/227

---

I have performance problems, after updating.

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: gjs 1.54.3-1build1
Uname: Linux 5.0.0-050000rc6-generic x86_64
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 18 07:39:11 2019
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2018-12-02 (77 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcCmdline: gjs /<email address hidden>/service/daemon.js
SegvAnalysis:
 Segfault happened at: 0x7f224b1fafd8: mov (%r15),%edx
 PC (0x7f224b1fafd8) ok
 source "(%r15)" (0xfff9800000000002) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gjs
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_socket_receive_message () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ?? () from /usr/lib/libgjs.so.0
Title: gjs-console crashed with SIGSEGV in g_socket_receive_message()
UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

[Apport retracing service (apport)]

StacktraceTop:
 g_socket_receive_message_with_timeout (socket=0x55e5a1d6c520, address=0x7ffd90139e98, vectors=0x7ffd90139c30, num_vectors=<optimized out>, messages=0x7ffd90139eb0, num_messages=0x7ffd90139eb8, flags=0xfff9800000000002, timeout_us=-1, cancellable=0x0, error=0x7ffd9013a060) at ../../../gio/gsocket.c:5203
 g_socket_receive_message (socket=<optimized out>, address=<optimized out>, vectors=<optimized out>, num_vectors=<optimized out>, messages=<optimized out>, num_messages=<optimized out>, flags=0xfff9800000000002, cancellable=0x0, error=0x7ffd9013a060) at ../../../gio/gsocket.c:5719
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x55e5a245e258, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x7ffd9013a058, avalue=avalue@entry=0x7ffd90139ee0) at ../src/x86/ffi64.c:525
 gjs_invoke_c_function (context=0x55e5a1a70670, function=0x55e5a245e240, obj=..., args=..., js_rval=..., r_value=0x0) at gi/function.cpp:1096

[Launchpad Janitor (janitor)]

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

[Daniel van Vugt (vanvugt)]

Also tracking in:

https://errors.ubuntu.com/problem/434b8b4abd971c7f84ca824ef5878a00d547753a

[Andrea Azzarone (azzar1)]

I proposed a fix upstream here: https://gitlab.gnome.org/GNOME/glib/merge_requests/710

[Sebastien Bacher (seb128)]

Reassigning to glib, if you mp that one in salsa Laney can probably help you to land it in Debian/sync over to Disco

[Andrea Azzarone (azzar1)]

We could also wait for glib 2.60.1 to be released (I think we also need to update gobject-introspection).

[Andrea Azzarone (azzar1)]

Fixed in gobject-introspection (1.60.0-1).