[kmail2] [Bug 345979] kmail stucks reegualary when syncing a gmail-imap-akonadi-ressource

[silentz0r]

https://bugs.kde.org/show_bug.cgi?id=345979

silentz0r <d.misdanitis at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |d.misdanitis at gmail.com

--- Comment #3 from silentz0r <d.misdanitis at gmail.com> ---
(In reply to Denis Kurz from comment #2)
> This bug has never been confirmed for a KDE PIM version that is based on KDE
> Frameworks (5.x). Those versions differ significantly from the old 4.x
> series. Therefore, I plan to close it in around two or three months. In the
> meantime, it is set to WAITINGFORINFO to give reporters the oportunity to
> check if it is still valid. As soon as someone confirms it for a recent
> version (at least 5.1, ideally even more recent), I'll gladly reopen it.
> 
> Please understand that we lack the manpower to triage bugs reported for
> versions almost two years beyond their end of life.

This bug stills exists. I'm on whatever version is currently on Arch Linux's
upstream repositories which is fairly up-to-date. This does not even happen for
such large collections, I've had this happen on my work mail which is less than
400MB (0.33 GB (2%) of 15 GB used, per gmail's quota).

This is not an old migrated setup either, the PC was wiped clean less than 6
months ago and everything was reinstalled.

I've noticed that one specific folder which contains over 1,000 emails is the
one that gets stuck when syncing. After restarting akonadi manually (akonadictl
restart) and hitting the sync button, Kmail starts syncing my folders one by
one and eventually gets to the large folder, which only goes up to 84% IIRC.
Maybe this helps track down some resource which would crash on anything above
800-900 emails (84% of 1100) or maybe it's just an unrelated visual while
akonadi crashes.

This seems like akonadi hangs when any task gets stuck, which is pretty bad. It
has also been confirmed by a KDE dev on the forums:
https://forum.kde.org/viewtopic.php?f=215&t=139394#p375588

-- 
You are receiving this mail because:
You are the assignee for the bug.