https://bugs.kde.org/show_bug.cgi?id=484837
MartinG <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #7 from MartinG <[email protected]> --- Created attachment 184276 --> https://bugs.kde.org/attachment.cgi?id=184276&action=edit gdb backtrace of kactivitymanagerd while cpu runs high I have the same problem: kactivitymanagerd spikes on high CPU usage on one core. I have investigated a bit: I can get kactivitymanager to work on low cpu by doing: $ systemctl --user restart plasma-kactivitymanagerd.service but once I switch between activities, by using my custom shortcut meta+tab (“Walk through activities”), the CPU spikes and stays high. This is a ltrace: $ ltrace -p $(pidof kactivitymanagerd) _ZN14QReadWriteLock14tryLockForReadE14QDeadlineTimer(0x55d3a27f3568, 0x7fffffffffffffff, 0x100000000, 0x7ffdc8b92d90) = 1 _ZN14QReadWriteLock6unlockEv(0x55d3a27f3568, 0x7fffffffffffffff, 0x55d3a2865c40, 0x55d3a28080c0) = 1 _ZN14QReadWriteLock14tryLockForReadE14QDeadlineTimer(0x55d3a27f3568, 0x7fffffffffffffff, 0x100000000, 0x7ffdc8b92d90) = 1 _ZN14QReadWriteLock6unlockEv(0x55d3a27f3568, 0x7fffffffffffffff, 0x55d3a2865c40, 0x55d3a28080c0) = 1 _ZN14QReadWriteLock14tryLockForReadE14QDeadlineTimer(0x55d3a27f3568, 0x7fffffffffffffff, 0x100000000, 0x7ffdc8b92d90) = 1 _ZN14QReadWriteLock6unlockEv(0x55d3a27f3568, 0x7fffffffffffffff, 0x55d3a2865c40, 0x55d3a28080c0) = 1 _ZN14QReadWriteLock14tryLockForReadE14QDeadlineTimer(0x55d3a27f3568, 0x7fffffffffffffff, 0x100000000, 0x7ffdc8b92d90) = 1 _ZN14QReadWriteLock6unlockEv(0x55d3a27f3568, 0x7fffffffffffffff, 0x55d3a2865c40, 0x55d3a28080c0) = 1 _ZN14QReadWriteLock14tryLockForReadE14QDeadlineTimer(0x55d3a27f3568, 0x7fffffffffffffff, 0x100000000, 0x7ffdc8b92d90) = 1 And a gdb backtrace is attached (' gdb -batch -ex "thread apply all bt" -p $(pidof kactivitymanagerd)') -- You are receiving this mail because: You are watching all bug changes.
