gjs-console crashed with SIGSEGV in JS_GetContextPrivate()

Bug #1761945 reported by Jesse
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gjs (Ubuntu)
New
Undecided
Unassigned

Bug Description

Unsure what produced this crash/issue.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gjs 1.52.0-1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sat Apr 7 00:54:51 2018
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2018-04-07 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-documents --gapplication-service
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f7593c232e4 <_Z20JS_GetContextPrivateP9JSContext+4>: mov 0x8e28(%rdi),%rax
 PC (0x7f7593c232e4) ok
 source "0x8e28(%rdi)" (0x00008e28) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gjs
StacktraceTop:
 JS_GetContextPrivate(JSContext*) () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
 _gjs_context_is_sweeping () at /usr/lib/libgjs.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
Title: gjs-console crashed with SIGSEGV in JS_GetContextPrivate()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Jesse (jessedubord) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1751194, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.