gnome-shell crashed with SIGSEGV in js::GCMethods<JSObject*>::needsPostBarrier()

Bug #1689863 reported by Per-Inge
220
This bug affects 35 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

https://errors.ubuntu.com/problem/858749eabf2fe619e12002e9f13cb2586b61d781
and
https://errors.ubuntu.com/problem/d281488b75322ce41fbfbb73416a6730da093b40

---

Kodi and Chrome was running. It happened when I was looking at a video played by Kodi. I didn't use keyboard or mouse.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.24.1-0ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu6
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Wed May 10 18:20:24 2017
DisplayManager: lightdm
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1493296359
InstallationDate: Installed on 2017-04-29 (11 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170428)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/p-i
SegvAnalysis:
 Segfault happened at: 0x7f164beeb105: testb $0x1,(%rax)
 PC (0x7f164beeb105) ok
 source "$0x1" ok
 destination "(%rax)" (0x7f15e3cfffe8) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/libgjs.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 meta_run () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0
Title: gnome-shell crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Per-Inge (per-inge-hallin) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 js::GCMethods<JSObject*>::needsPostBarrier (v=0x7f15e3c18640) at /usr/include/mozjs-38/js/RootingAPI.h:663
 JS::Heap<JSObject*>::set (newPtr=0x0, this=0x5627df7e2200) at /usr/include/mozjs-38/js/RootingAPI.h:296
 JS::Heap<JSObject*>::operator= (p=<optimized out>, this=0x5627df7e2200) at /usr/include/mozjs-38/js/RootingAPI.h:266
 GjsMaybeOwned<JSObject*>::reset (this=0x5627df7e21f0) at ./gjs/jsapi-util-root.h:266
 closure_clear_idle (data=0x5627df7e21c0) at gi/closure.cpp:132

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
summary: - gnome-shell crashed with SIGSEGV in g_main_context_dispatch()
+ gnome-shell crashed with SIGSEGV in
+ js::GCMethods<JSObject*>::needsPostBarrier()
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
description: updated
tags: added: zesty
Revision history for this message
Yu (nasa-yjh2012) wrote :

Hi everybody! I'm a new linux user.
there is any solution for this bug?
here is my '$dmesg' output:
----------------------------------------------------------------
[92918.138138] gnome-shell[28983]: segfault at 7fd623bfffe8 ip 00007fd6bfff7ed5 sp 00007ffdd554ab80 error 4 in libgjs.so.0.0.0 (deleted)[7fd6bffcd000+bc000]
[93005.945159] gnome-shell[3350]: segfault at 7f82f3dfffe8 ip 00007f8370a2e735 sp 00007fff3659e3e0 error 4 in libgjs.so.0.0.0[7f8370a03000+bc000]
----------------------------------------------------------------
this bug did cause the pc reboot, seems just restarted gnome..
and closed all my windows like chromium... terminals...
It's really annoying.
Need Help!!!
If any suggestion, plz send to me a email:<email address hidden>

description: updated
Revision history for this message
BytEvil (itemcode) wrote :

Same problem on my Arch Linux system.

--------------------------------------------------------------------------------------
Jun 29 09:13:56 KODI kernel: [166781.847233] gnome-shell[4988]: segfault at 7ff0dfffffe8 ip 00007ff13f8c2625 sp 00007fffa3d158a0 error 4 in libgjs.so.0.0.0[7ff13f897000+bc000]
Jun 29 09:13:56 KODI gnome-session[1821]: gnome-session-binary[1821]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Jun 29 09:13:56 KODI gnome-session-binary[1821]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
--------------------------------------------------------------------------------------

Revision history for this message
L.F. Moisa (florin-moisa) wrote :

Same problem here, happens once in a while (several times a day), it restarts the window manager:
--------------------------------------------------------------------------------------
Dec 17 00:51:33 server kernel: [312304.994059] gnome-shell[25564]: segfault at 7f1eac1fffe8 ip 00007f1f397b43d5 sp 00007ffc5d9fb600 error 4 in libgjs.so.0.0.0[7f1f3978c000+ba000
]
Dec 17 00:51:33 server gnome-session[4492]: gnome-session-binary[4492]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Dec 17 00:51:33 server gnome-session-binary[4492]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Dec 17 00:51:33 server /usr/lib/gdm3/gdm-x-session[4479]: (--) NVIDIA(GPU-0): DFP-0: disconnected
Dec 17 00:51:33 server /usr/lib/gdm3/gdm-x-session[4479]: (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
Dec 17 00:51:33 server /usr/lib/gdm3/gdm-x-session[4479]: (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
Dec 17 00:51:33 server /usr/lib/gdm3/gdm-x-session[4479]: (--) NVIDIA(GPU-0):
--------------------------------------------------------------------------------------

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Fix Released. Zero reports of this crash after Ubuntu 17.10.

Changed in gnome-shell (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.