gjs-console crashed with SIGSEGV in JSAutoCompartment::JSAutoCompartment()
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
ProcVersionSign
Uname: Linux 4.13.0-
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Classic:GNOME
Date: Fri Oct 20 11:21:02 2017
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-02-06 (255 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
ProcCmdline: /usr/bin/
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
LANGUAGE=en_GB:en
PATH=(custom, user)
LANG=en_GB.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f15a955f1a2 <_ZN17JSAutoCom
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:
JSAutoCompartm
?? () from /usr/lib/
ffi_closure_
ffi_closure_unix64 () from /usr/lib/
?? () from /usr/lib/
Title: gjs-console crashed with SIGSEGV in JSAutoCompartme
UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)
UserGroups: adm docker lpadmin sambashare sudo
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.