gjs-console assert failure: free(): invalid pointer

Bug #1968440 reported by Syed Umair Ali
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gjs (Ubuntu)
New
Undecided
Unassigned

Bug Description

I was browsing the web and this popup came up saying that gjs-console had stopped working.

My system specs

OS: Ubuntu 22.04 lts beta
Processor: Intel Core i5-4220M
GPU: IntelHD 4600
RAM: 16Gigs
Gnomeversion: 42
Windowsing system: Wayland.

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gjs 1.72.0-1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
AssertionMessage: free(): invalid pointer
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 10 01:00:37 2022
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2022-04-09 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcCmdline: /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Extensions
RebootRequiredPkgs: Error: path contained symlinks.
Signal: 6
SourcePackage: gjs
StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f8b3637ab8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155
 malloc_printerr (str=str@entry=0x7f8b36378764 "free(): invalid pointer") at ./malloc/malloc.c:5664
 _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at ./malloc/malloc.c:4439
 __GI___libc_free (mem=<optimized out>) at ./malloc/malloc.c:3391
 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
Title: gjs-console assert failure: free(): invalid pointer
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

Revision history for this message
Syed Umair Ali (syedumaircodes) 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 #1946165, 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.

Other bug subscribers

Remote bug watches

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