Comment # 5 on bug 1182982 from Fabian Vogt

(In reply to Richard Weinberger from comment #4)
> But the process consumes 100% CPU all the time. Also when noting is logged
> (which is most the time the case).
> 
> Additionally I run "perf top" on the imap resource process at the point
> where it consumed 100% CPU:
>   96.95%  libQt5Core.so.5.12.7            [.]
> QMetaObjectPrivate::disconnectHelper

Now that's actually interesting. It shows that the process isn't busy
processing mail data, but with handling disconnections. This reminds me very
much of https://bugreports.qt.io/browse/QTBUG-72649.

Looking at the akonadi code, it's prone to run into the pretty much worst case
of this:
https://github.com/KDE/akonadi/blob/3bbbdfb368e36b3866a9b58e282120a65e1074a9/src/core/connection.cpp#L247

If this is the case, it also explains why so far we weren't able to reproduce
this issue: It becomes worse the longer the process is running and the more
requests it receives.

>    1.39%  libQt5Core.so.5.12.7            [.] QMetaObject::activate