[Bug 1908429] Re: 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 conn
In addition to my previous entry (I can't seem to edit it), I'd like to say the "unbearable" switching from window to window means 5-15 seconds. For me, this flood of errors appears as the end result of something else taking place. For me, that only started after the observed drastic sluggishness of the UI. That had happened before, though I didn't check any logs. Actually with qbittorrent, there was no obvious high system load, and digikam did perform well in the background (memory usage also no more than 60-70%) as the progress showed (up to 14:45) -- 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
[Bug 1908429] Re: 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 conn
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
Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
I can confirm it working (yahoo). Thanks for the efforts! After running apt upgrade and seeing amongst others, things were fine: Get:10 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libgnutlsxx28 amd64 3.5.18-1ubuntu1.4 [13,7 kB] Get:11 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libgnutls28-dev amd64 3.5.18-1ubuntu1.4 [660 kB] Get:12 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libgnutls-dane0 amd64 3.5.18-1ubuntu1.4 [21,0 kB] Get:13 http://de.archive.ubuntu.com/ubuntu bionic-updates/main i386 libgnutls30 i386 3.5.18-1ubuntu1.4 [660 kB] Get:14 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libgnutls30 amd64 3.5.18-1ubuntu1.4 [645 kB] On Thu, 2020-07-02 at 14:56 +, Launchpad Bug Tracker wrote: > This bug was fixed in the package gnutls28 - 3.4.10-4ubuntu1.8 > > --- > gnutls28 (3.4.10-4ubuntu1.8) xenial; urgency=medium > > * d/p/50_Update-session_ticket.c-to-add-support-for-zero-leng.patch: > - add support for zero length session tickets returned from the server, > thanks Rod for the backport and testing! (lp: #1876286) > > -- Sebastien Bacher Wed, 17 Jun 2020 23:06:13 > +0200 > > ** Changed in: gnutls28 (Ubuntu Xenial) >Status: Fix Committed => Fix Released > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
It is obviously related to yahoo for all of us, but that does not mean Yahoo caused it. While it might be that Yahoo has done some changes, I have other mail clients (Thunderbird on Ubuntu, K9 on Android, Mailmate on Mac) that have not been updated and have had no problem with yahoo. We are very specifically looking at Evolution in relation to Yahoo. Two mere suspicions, and I have no way to check due to lack of knowledge, a) there was an update on Ubuntu that caused the issue. b) indeed, yahoo did some changes, but they were no problem before. Whatever library in the background handles this, worked fine so far, but could not cope with this hypothetical change. Then it must be that Thunderbird works differently. cheers, Martin On Fri, 2020-05-15 at 14:17 +, richard wrote: > This same problem started the first week of May with my IMAP+ AT&T. "Error > performing TLS handshake: ..." > Ubuntu Mate 16 Evolution 3.18.5.2-0ubuntu3.2 > > Sending SMTP still works. > > Reading through the posts it's clear that it's a Yahoo issue since Yahoo > manages AT&T, AOL, Verizon and Yahoo mail and those are the only ones > affected. > > Why has no fix-update been created yet? > It's not like people are so swamped with work they don't have time to. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
I'll just chime in with a "me too". Connecting to imap yahoo fails. A couple of other accounts work fine. I changed no mail settings. However some Ubuntu (18.04) updates ran. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
