gjs-console crashed with SIGSEGV in JSAutoCompartment::JSAutoCompartment()

Bug #1716688 reported by Zomite Akora on 2017-09-12
This bug affects 14 people
Affects Status Importance Assigned to Milestone
gjs (Ubuntu)

Bug Description

gjs-console crashed with SIGSEGV in JSAutoCompartment::JSAutoCompartment()

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gjs 1.49.92-1
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Tue Sep 12 18:43:37 2017
ExecutablePath: /usr/bin/gjs-console
ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-documents --gapplication-service
 Segfault happened at: 0x7fc21e57d1a2 <_ZN17JSAutoCompartmentC2EP9JSContextP8JSObject+18>: mov (%rdx),%rax
 PC (0x7fc21e57d1a2) ok
 source "(%rdx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gjs
 JSAutoCompartment::JSAutoCompartment(JSContext*, JSObject*) () from /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
 ?? () from /usr/lib/libgjs.so.0
 ffi_closure_unix64_inner () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_closure_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gjs-console crashed with SIGSEGV in JSAutoCompartment::JSAutoCompartment()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Zomite Akora (zokarata) wrote :

 JSAutoCompartment::JSAutoCompartment (this=0x7fc1d57f94b0, cx=0x556e1130a550, target=0x0) at ./js/src/jsapi.cpp:719
 gjs_callback_closure (cif=<optimized out>, result=0x7fc1d57f9910, args=0x7fc1d57f9770, data=0x556e11ceb180) at gi/function.cpp:211
 ffi_closure_unix64_inner (closure=0x7fc214000410, rvalue=0x7fc1d57f9910, reg_args=0x7fc1d57f9860, argp=0x7fc1d57f9930 "\020\071+\334\301\177") at ../src/x86/ffi64.c:670
 ffi_closure_unix64 () at ../src/x86/unix64.S:229
 g_task_return_now (task=0x7fc1dc2b3910) at ../../../../gio/gtask.c:1145

Changed in gjs (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report. Can you provide steps to reproduce this issue?

information type: Private → Public
Changed in gjs (Ubuntu):
status: New → Incomplete
Zomite Akora (zokarata) wrote :

Unfortunately I can't.

Zomite Akora (zokarata) wrote :

I did switch from gnome into unity and it reproduced.

Jean-Baptiste Lallement (jibel) wrote :

Do you have a script or a set of commands that you're running in gjs and would trigger this bug?

Changed in gjs (Ubuntu):
status: Incomplete → Confirmed
Mario Abarca (knkillname) wrote :

I got this error by doing nothing in particular. I was just checking Facebook on Google Chrome when the error message popped up. Sadly I had just made a fresh install of Ubuntu 17.10 and then installed a lot of metapackages which I need to work.

tags: added: bionic
Ashwin (ashwinjmathew) wrote :

I get this error as well. Nothing in particular seems to trigger it - my Gnome session just crashes. Sometimes while I'm working, sometimes while I've stepped away from my laptop.

I'm on Ubuntu 17.10 with all current updates applied.

Belmar-Letelier (luis-c) wrote :

same for me on bionic

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers