SUMMARY STEPS TO REPRODUCE 1. Just have an uptime more than 10 days OBSERVED RESULT CPU at 100%, 16-64GB of memory used ADDITIONAL INFORMATION [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x00007eff3b92e7ed in __GI___poll (fds=0x5560a58c9f90, nfds=3, timeout=426982) at ../sysdeps/unix/sysv/linux/poll.c:29 29 ../sysdeps/unix/sysv/linux/poll.c: No such file or directory. (gdb) bt #0 0x00007eff3b92e7ed in __GI___poll (fds=0x5560a58c9f90, nfds=3, timeout=426982) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x00007eff3a119e7e in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #2 0x00007eff3a119f9f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007eff3bf56e22 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x5560a580fcd0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x00007eff3bf0041b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffc03dc6350, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x00007eff3bf08437 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #6 0x00007eff3cf1846e in Akonadi::ResourceBase::init(Akonadi::ResourceBase&) () at /usr/lib64/libKF5AkonadiAgentBase.so.5 #7 0x00005560a3ccd082 in int Akonadi::ResourceBase::init<KAlarmResource>(int, char**) () #8 0x00007eff3b85de35 in __libc_start_main (main= 0x5560a3cbf3e0 <main>, argc=3, argv=0x7ffc03dc65c8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc03dc65b8) at ../csu/libc-start.c:308 #9 0x00005560a3cbf41a in _start () at ../sysdeps/x86_64/start.S:120
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)