Version: 2.0 beta1 (using Devel) OS: Linux First of all, I do not know where this bug should be placed. dbus, akonadi or kmail2. When syncing a folder (the gmail total folder) with around 50.000 mails stored, akonadi_imap seems to use dbus to comunicate with kmail2 or whatever. In a normal session, dbus cpu usage is < 1%. In this situation, dbus cpu usage is >20%. At some time, plasma makes a dbus call and it is so far in the dbus queue that looks blocked. The same happens to kscreenlock when it wants to show the unlock dialog. Changing akonadi_imap nice to 20 alleviates the problem a little bit, but it will happen again and again. Reproducible: Always Steps to Reproduce: to have stored a lot of kmail bugs mails. Expected Results: reduce the dbus usage or make dbus use several queues (or a special queue for akonadi)
Created attachment 49610 [details] pstack output
Created attachment 49611 [details] valgring output
(Please ignore the previous attachments, bugzilla jumped to the wrong bug. Sorry for the noise)
Could you provide a bit of dbus-monitor output so we can see what messages exactly are sent there? Do you happen to have akonadiconsole running or have the protocol debugger enabled (~/.config/akonadi/akonadiserverrc, [Debug]\nTracer=dbus)? Both can increase D-Bus usage massively.
I see no more that amount of dbus usage, even with >50.000 mails.