gjs-console crashed with SIGSEGV in JS_GetContextPrivate()

Bug #1762829 reported by Rachel Greenham
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

was mostly using synaptic, choosing packages to remove, but hadn't removed them yet. had just quit totem, this came up a few seconds later. No other apparent symptoms.

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
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 10 21:33:26 2018
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2017-08-07 (246 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-documents --gapplication-service
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f28cb8262e4 <_Z20JS_GetContextPrivateP9JSContext+4>: mov 0x8e28(%rdi),%rax
 PC (0x7f28cb8262e4) 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*) () from /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
 _gjs_context_is_sweeping () from /usr/lib/libgjs.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
Title: gjs-console crashed with SIGSEGV in JS_GetContextPrivate()
UpgradeStatus: Upgraded to bionic on 2018-03-10 (31 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Rachel Greenham (rachel-strangenoises) 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.