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

[Reiner B.]

Upgrade from 17.10 to 18.04. Crash happens after first start.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gjs 1.50.2-2
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Jan 13 15:37:43 2018
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2016-08-24 (506 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-documents --gapplication-service
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fb079256702 <_ZN17JSAutoCompartmentC2EP9JSContextP8JSObject+18>: mov (%rdx),%rax
 PC (0x7fb079256702) 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*) () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
 () at /usr/lib/libgjs.so.0
 ffi_closure_unix64_inner () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_closure_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gjs-console crashed with SIGSEGV in JSAutoCompartment::JSAutoCompartment()
UpgradeStatus: Upgraded to bionic on 2018-01-13 (0 days ago)
UserGroups: adm cdrom dip lpadmin lxd 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.