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

[Matthijs Kooijman]

I was working with gnome-extensions-app and the gnome-screenshot extension, and then this "report a bug" popup popped up. I'm not entirely sure what I did to cause this crash. I have seen this (or a similar) crash a few times before, but then it refused to send a report because I had pending updates (which are now installed).

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gjs 1.72.0-1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
AssertionMessage: free(): invalid pointer
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 9 16:55:36 2022
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2022-04-08 (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=0x7f11d1054b8c "%s\n") at ../sysdeps/posix/libc_fatal.c:155
 malloc_printerr (str=str@entry=0x7f11d1052764 "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 dialout dip docker libvirt lpadmin lxd plugdev sambashare sudo wireshark
separator:

[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 #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.