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

Bug #1718853 reported by Zomite Akora
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gjs (Ubuntu)
New
Undecided
Unassigned

Bug Description

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

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gjs 1.50.0-1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Sep 22 09:57:40 2017
ExecutablePath: /usr/bin/gjs-console
ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-documents --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7fcd5eeac1a2 <_ZN17JSAutoCompartmentC2EP9JSContextP8JSObject+18>: mov (%rdx),%rax
 PC (0x7fcd5eeac1a2) 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
StacktraceTop:
 JSAutoCompartment::JSAutoCompartment(JSContext*, JSObject*) () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
 () at /usr/lib/libgjs.so.0
 ffi_closure_unix64_inner () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_closure_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 () at /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

Revision history for this message
Zomite Akora (zokarata) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1716688, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
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.