Summary: | plasmashell using 100% CPU time | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | crog |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | bhush94, dimanne, kolAflash, plasma-bugs, rdieter |
Priority: | NOR | ||
Version: | 5.5.5 | ||
Target Milestone: | 1.0 | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
crog
2016-06-07 14:17:32 UTC
Same for me. Bug report - https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1592668 Plasmashell thread http://pastebin.com/CZtfCq7m Xorg thread http://pastebin.com/eAi9Ua9N Was anything animating at the time of CPU spike? A busy logo spinning for example. No. No animations, no blinking icons at the time of CPU spike. By the way, I found workaround - I just cleared all kde settings (~/.kde, ~/.config/<many files>, ~/.local/share/<something else>) and the problem has gone. All is working perfectly now. I have recently encountered this problem again at my notebook. System info: plasmashell 5.5.5 OS: Kubuntu 16.04 Also, I have two (physical) monitors, and I noticed this problem began to arise after I detached/attached notebook from dock station or after hibernation Backtraces, perf top: I ran "top -H" and it said there are two threads on my system, which are eating CPU - plasmashell and Xorg, so here is "hottest" backtraces of these threads collected with perf top -t 3136 -d 5 --call-graph dwarf (where 3136 is thread Id from top output) Thread of plasmashell - http://pastebin.com/GPMkrWz8 (see text after RAW Paste Data) Thread of Xorg - http://pastebin.com/ZH0x7F7i (see text after RAW Paste Data) Backtrace shows it literally idling. Thread 1 (Thread 0x7f00f0173900 (LWP 3410)): #0 0x00000037952f757d in poll () at ../sysdeps/unix/syscall-template.S:81 At the point in that snap it is not using any CPU. As for perf.top, it's the same as the rendering one, that I'm marking this as a dupe of. Sometimes between X, Mesa and Qt on some drivers it just starts drawing at infinite frames per second. It requires someone with the problem to spend some time putting in debug into all 3 parts at once to identify why. No log is going to help. Apparently running with "QSG_RENDER_LOOP=threaded plasmashell" doesn't hit this issue, and is ultimately much faster and where we're heading towards anyway. *** This bug has been marked as a duplicate of bug 356479 *** One more observation. I have encountered this bug twice recently, and I managed to workaround this bug by erasing all user-specific config files of KDE |