gjs-console crashed with SIGSEGV in JSAutoCompartment::JSAutoCompartment()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gjs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
no idea, keep getting this error
1) lsb_release -rd
Description: Ubuntu Artful Aardvark (development branch)
Release: 17.10
2) apt-cache policy gjs
gjs:
Installed: 1.50.1-1
Candidate: 1.50.1-1
Version table:
*** 1.50.1-1 500
500 http://
100 /var/lib/
3) unknown
4) unknown
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gjs 1.50.1-1
ProcVersionSign
Uname: Linux 4.13.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Oct 6 10:30:37 2017
ExecutablePath: /usr/bin/
ExecutableTimes
InstallationDate: Installed on 2016-03-03 (589 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
ProcCmdline: /usr/bin/
ProcCwd: /home/nick
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7fed3c72b1a2 <_ZN17JSAutoCom
PC (0x7fed3c72b1a2) 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:
JSAutoCompartm
() at /usr/lib/
ffi_closure_
ffi_closure_unix64 () at ../src/
() at /usr/lib/
Title: gjs-console crashed with SIGSEGV in JSAutoCompartme
UpgradeStatus: Upgraded to artful on 2017-10-03 (9 days ago)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
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.