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

Bug #1725284 reported by Chris Wall
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gjs (Ubuntu)
New
Undecided
Unassigned

Bug Description

error popped up

let me know if I should stop reporting these...

<email address hidden>

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gjs 1.50.1-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
Uname: Linux 4.13.0-16-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Classic:GNOME
Date: Fri Oct 20 11:21:02 2017
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2017-02-06 (255 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-documents --gapplication-service
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f15a955f1a2 <_ZN17JSAutoCompartmentC2EP9JSContextP8JSObject+18>: mov (%rdx),%rax
 PC (0x7f15a955f1a2) 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*) () 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: Upgraded to artful on 2017-10-20 (0 days ago)
UserGroups: adm docker lpadmin sambashare sudo

Revision history for this message
Chris Wall (hypnoboutique) 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.