I can confirm the same effect for myself, Ubuntu 20.04 grep -n -m 1 '8 23:58:00' syslog.1 843618574:Jan 8 23:58:00 smallbox gnome-shell[3313]: The offending callback was SourceFunc()
$ grep -n -m 1 '8 23:59:00' syslog.1 845405757:Jan 8 23:59:00 smallbox gnome-shell[3313]: The offending callback was SourceFunc(). That is close to 1.8 Million entries per minute. Eventually the disk was full after 250GB of logs. Background: I had in the past (also with 18.04) noticed that the UI gets very sluggish at occasions, e.g. when running qbittorrent for some days. At this time digikam (7.2beta) was running its face recognition (I allowed all CPUs) using 70-90% CPU. There is a high amount of disk I/O. Initially that caused no significant impact on the usage. After about 5 hours, the UI got sluggish, after 24h it became unbearable to click from one window to another. I disabled the screenlock (logging in took about 2 min by now). At about 14:45 waking up the screen, displayed the favorites bar plus the big clock (frozen) on fuzzy background, a login field did not appear. Hoping at least digikam would finish, I left it until the next morning. After a power-off and some hassles of clearing disk space, I had working machine again. I have attached an extract of the syslog from around 14:45 when things went bad. If of interest, I still have the full syslogs and can find bits in there. I saw a similar issue here: https://github.com/GSConnect/gnome-shell- extension-gsconnect/issues/588, but I don't have gsconnect installed ** Bug watch added: github.com/GSConnect/gnome-shell-extension-gsconnect/issues #588 https://github.com/GSConnect/gnome-shell-extension-gsconnect/issues/588 ** Attachment added: "syslog.1.extract" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908429/+attachment/5451405/+files/syslog.1.extract -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908429 Title: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was SourceFunc(). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
