Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem: Customer reports recurrent errors of the following filling up the syslog:
Mar 28 00:00:00 localhost gnome-shell[2408549]: 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.
Mar 28 00:00:00 localhost gnome-shell[2408549]: The
offending signal was notify on GnomeWallClock 0x55ba1f528610.
Mar 28 00:00:00 localhost org.gnome.Shell.desktop[2408549]:
== Stack trace for context 0x55ba16a24280 ==
Mar 28 00:00:01 localhost gnome-shell[2408549]: 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.
Mar 28 00:00:01 localhost org.gnome.Shell.desktop[2408549]:
== Stack trace for context 0x55ba16a24280 ==
Mar 28 00:00:01 localhost gnome-shell[2408549]: The
offending signal was notify on GnomeWallClock 0x55ba1f528610.
The events simply fill the logs. The user interface is non-responsive.
Version-Release number of selected component (if applicable):
3.32.2-48.el8
How reproducible: No solid reproducer available; behavior seems to be random, but consistent with https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1868 .
Additional info: