syslog filling up

[[e-mail]]

─| lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04

└─| apt-cache policy gnome-shell
gnome-shell:
  Installed: 42.9-0ubuntu2
  Candidate: 42.9-0ubuntu2
  Version table:
 *** 42.9-0ubuntu2 500
        500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     42.0-2ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

No gnome extensions installed. very limited use of the desktop as most everything is manages thru ssh remotely.

The error causes /var/log/syslog file to rapidly grow until the disk is full.

The following line are repeated thousands and thousands of times in the syslog file.

z440 gnome-shell: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
z440 gnome-shell: The offending signal was notify on GnomeWallClock 0x55c4f6b7d830.
z440 nxpreload.sh: == Stack trace for context 0x55c4f52f64a0 ==

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2 [modified: usr/share/applications/org.gnome.Shell.desktop]
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Jan 25 21:07:01 2024
DisplayManager: gdm3
InstallationDate: Installed on 2023-10-29 (89 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.9-0ubuntu5
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

Does it always follow with "The offending signal was notify on GnomeWallClock"?

Can you attach a log showing the problem in detail?

See also similar bug 2042909, bug 1994125, bug 1908429 and https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2760