GNOME Bugzilla – Bug 766547
Geary RAM usage keeps growing as app syncs emails
Last modified: 2018-04-10 06:20:30 UTC
As geary is open and syncing emails it consistently grows in its memory usage. When initially adding accounts the ram usage increased to upwards of 500MB on one of my computers, and I saw it reach a peak of 600MB on another. Further the app doesn't seem to release these resources during the life of the application. Once rebooting the application Geary usually starts its life around 80-90MB, but as I open folders that have unloaded emails, or I scroll to force updating of emails, the app usage grows continuously, while again not releasing the resources. The initial import is when the memory usage is the worst, during a normal session (after initial mass import) I have gotten it up to 170MB, and over 30 min of letting it sit open idle the ram usage only dropped by ~5MB. Note* I didn't test after the initial account adding whether or not the RAM usage would slowly drop. Instead after it got to 600MB I killed the app and reopened it, at which point the app was only using ~80MB.
Letting it sit open, the app is now at 305MB, and was sitting at 9% CPU usage. I am assuming it is syncing still,
15 min later the app is now at 340MB just sitting idle
If you start geary with "-d", let it do the initial sync (this may take a few minutes), what does it report it is doing when idle?
It just continuously outputs these four lines: [deb] 23:19:24 7.065652 imap-client-session-manager.vala:525: Checking if IMAP host imap.gmail.com/default:993 reachable... [deb] 23:19:24 0.000109 imap-client-session-manager.vala:525: Checking if IMAP host imap.gmail.com/default:993 reachable... [msg] 23:19:24 0.000162 imap-client-session-manager.vala:536: IMAP host imap.gmail.com/default:993 considered reachable [msg] 23:19:24 0.000038 imap-client-session-manager.vala:536: IMAP host imap.gmail.com/default:993 considered reachable
Oh, that's weird. You aren't having any network connectivity issues, I assume? Can you run Geary with the command "geary -d | tee geary.out" until it starts doing that, quit the app, remove any personal info from the geary.out file, and post it here?
Nope I wasn't having network connection issues. I have the output, let me post it real quick
Created attachment 328090 [details] output of geary -d Here is the output of geary -d scrubbed for my personal info
Created attachment 329150 [details] [review] Patch to get some more debugging info Britt, can you please try rebuilding Geary with the attached patch applied to the source tree beforehand, then attaching a similar log. This will provide a bit of extra detail about what's happening with the network. Let me know if you need a hand doing that. Ta!
Maybe related to Bug 713134, since both relate to GMail and high CPU utilisation when idle.
Yes, when I got a free moment I will rebuild with the patch
Just a quick update, there's some investigation going on about the repeated "Checking if IMAP host ... reachable" debug output over in Bug 776042. This may be a glib issue. Also, a memory leak in glib related to this was fixed back in July: Bug 766933. This was released in glib 2.50, can you try upgrading to that and let me know if it resolves the memory leak you're seeing here?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment. Thanks!
Just FYI, this could be caused by a combination of Bug 778288 and . The former has been mitigated by work going on the master branch since 0.12 was released, so this situation may well improve substantially with that. I'd like to track down and fix the latter for 0.13 as well.
Err, I mean "... a combination of Bug 778288 and Bug 794995."