https://bugs.kde.org/show_bug.cgi?id=423406
--- Comment #5 from BRULE Herman ---
(KAlarm 3)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.kde.org/show_bug.cgi?id=423406
BRULE Herman changed:
What|Removed |Added
Resolution|--- |UNMAINTAINED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=423406
--- Comment #3 from David Jarvie ---
This doesn't happen on my system, so without more information on exactly where
in akonadi_kalarm_resource CPU is being used, I can't investigate.
This issue will go away in KAlarm version 3.0, which will no longer
https://bugs.kde.org/show_bug.cgi?id=423406
--- Comment #2 from BRULE Herman ---
Hi, 2-3 process on all process
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.kde.org/show_bug.cgi?id=423406
--- Comment #1 from David Jarvie ---
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
