Summary: | /usr/bin/akonadi_kalarm_resource --identifier akonadi_kalarm_resource_X put my cpu at 100% | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | BRULE Herman <alpha_one_x86> |
Component: | KAlarm resource | Assignee: | David Jarvie <djarvie> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | kdepim-bugs |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
BRULE Herman
2020-06-23 19:25:33 UTC
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. Hi, 2-3 process on all process 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 use Akonadi. It will be released as part of KDE release 20.08 in August. > KAlarm version 3.0, which will no longer use Akonadi
wonderfull! great! Then I will try KAlarm
(KAlarm 3) |