https://bugs.kde.org/show_bug.cgi?id=423406
--- Comment #1 from David Jarvie <djar...@kde.org> --- Did a single akonadi_kalarm_resource process use 100% CPU? If so, the stack trace doesn't help to find out why, since it gives no indication of where in the KAlarmResource it is hogging the CPU. -- You are receiving this mail because: You are on the CC list for the bug.
