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

[Ahmet A. Sabancı]

After installing some Gnome software in Ubuntu 17.10 (like Maps, Weather etc.) I rebooted and tried some. First checked Maps and closed it, than did the same with Weather. This error message showed up right after I closed Weather app.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gjs 1.50.1-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 15:31:27 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2017-10-03 (16 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-documents --gapplication-service
SegvAnalysis:
 Segfault happened at: 0x7f5cc63ab1a2 <_ZN17JSAutoCompartmentC2EP9JSContextP8JSObject+18>: mov (%rdx),%rax
 PC (0x7f5cc63ab1a2) 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-19 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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.