nettika/geary
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Don't avoid scheduling a second set of background idle GC work

Browse source 
This only happens once a day
This commit is contained in:
Chris Heywood 2020-05-29 16:51:27 +10:00
parent 95c68710d5
commit b080f8a49e
1 changed files with 1 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

11
src/engine/imap-engine/imap-engine-account-synchronizer.vala
View file

@ -16,7 +16,6 @@ private class Geary.ImapEngine.AccountSynchronizer :
private DateTime max_epoch = new DateTime(
new TimeZone.local(), 2000, 1, 1, 0, 0, 0.0
);
private bool background_idle_gc_scheduled = false;
public AccountSynchronizer(GenericAccount account) {
@ -100,17 +99,9 @@ private class Geary.ImapEngine.AccountSynchronizer :
private void old_messages_background_cleanup(GLib.Cancellable? cancellable) {
if (this.account.is_open() && !this.background_idle_gc_scheduled) {
this.background_idle_gc_scheduled = true;
if (this.account.is_open()) {
IdleGarbageCollection op = new IdleGarbageCollection(account);
op.completed.connect(() => {
this.background_idle_gc_scheduled = false;
});
cancellable.cancelled.connect(() => {
this.background_idle_gc_scheduled = false;
});
send_all(this.account.list_folders(), false, true, op);
// Add GC operation after message removal during background cleanup