gjs-console crashed with SIGSEGV in JSAutoCompartment::JSAutoCompartment()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gjs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
after open terminal maybe... im not sure!
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gjs 1.50.2-2
ProcVersionSign
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Jan 25 06:22:15 2018
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-09-02 (144 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7f06a1f40702 <_ZN17JSAutoCom
PC (0x7f06a1f40702) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin plugdev 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.