Re: GNOME Shell crash after opening and closing laptop lid several times
- From: Simon McVittie <smcv collabora com>
- To: gnome-shell-list gnome org
- Subject: Re: GNOME Shell crash after opening and closing laptop lid several times
- Date: Fri, 27 Oct 2017 11:31:23 +0100
Please report this crash as a gnome-shell bug on GNOME Bugzilla, and/or
to your OS vendor, if there is not already a matching bug report.
If you report it to both projects (or find matching bug reports in both
already), please leave a link to each bug report in the other one.
On Thu, 26 Oct 2017 at 17:26:22 +0200, Michael Thayer wrote:
I have a core file locally which I will keep around for a while,
though the symbols may not match perfectly.
...
#2 0x0000558f99b527b5 in default_log_handler
(log_domain=log_domain@entry=0x7f4504ce118e "GLib",
log_level=log_level@entry=6, message=message@entry=0x558f9f10eb90
"../../../../glib/gmem.c:130: failed to allocate 18446744072098939136
bytes", data=data@entry=0x0) at ../src/main.c:311
This looks quite a lot like
<https://bugzilla.gnome.org/show_bug.cgi?id=788627> which is apparently
related to <https://bugzilla.gnome.org/show_bug.cgi?id=788908>.
#2 0x00007f4502f2d072 in __pthread_cond_wait (cond=0x558f9ac51b90,
mutex=0x558f9ac78c50) at pthread_cond_wait.c:655
#3 0x00007f44fb7da864 in () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
#4 0x00007f44fb7daab5 in () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
#5 0x00007f44fbbd0d15 in () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
#6 0x00007f44fbbf1352 in () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
#7 0x00007f4502f267fc in start_thread (arg=0x7f44be7fc700)
Hopefully these threads aren't related to the crash, but in case they
become relevant: this is impossible to analyze without debug symbols,
so if these threads become interesting, you would have to install debug
symbols for mozjs and get the backtrace again. From the filename this
looks like Debian or Ubuntu, so you should be able to get debug symbols
by installing libmozjs-52-0-dbgsym (from the debian-debug archive if
you are on Debian, see https://deb.debian.org/) and analyze the core
with gdb again.
smcv
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]