If I log on to kde, the kde workspace gets slower and slower while the processor load increases dramatically even if there only light applications are running. Only the kde task bar and the and the k-menue are affected. Applications like Firefox, Thunderbird, Terminal, etc. are running normal. I have to use GNOME instead because this desktop is running fine. My CPU is a AMD FX-8350 eight core processor. Reproducible: Always Steps to Reproduce: 1. Choose KDE on login window 2. Log on 3. Wait Actual Results: KDE gets slower and slower. The CPU load on changes on the CPU cores. One of them is always at 100% during the other cores are normal. Expected Results: CPU load should be balanced
Created attachment 86185 [details] CPU loads
Could you please check with "top" or Ctrl+Esc which processes are consuming CPU time?
Created attachment 86236 [details] kdeproblem.png Seems to be the plasma-desktop process. It is consuming more and more CPU power without any reason Am 20.04.2014 23:33, schrieb Christoph Feck: > https://bugs.kde.org/show_bug.cgi?id=333653 > > Christoph Feck <christoph@maxiom.de> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |christoph@maxiom.de > > --- Comment #2 from Christoph Feck <christoph@maxiom.de> --- > Could you please check with "top" or Ctrl+Esc which processes are consuming CPU > time? >
Which version of kde-workspace are you using? Could you try removing some widgets to see which one causes the issue? Does it also happen with a freshly created user account?
I am running KDE 4.13 under Kubuntu 14.04 and I think what I am experiencing could be related with this bug report.. what is happening is plasma-desktop taking 100% of a CPU processing some Activity changes. I just right click on a window title bar and unselected some activity this window was displayed on. plasma-desktop goes 100%, I can still open the light ksysguard using CTRL-ESC alt-tab still works because it's kwin I presume all apps on the current activity works fine but plasma panel is brozen and I can no longer switch activity. eventually plasma-desktop finish his task and everything gets back to normal. thank you
Same issue, takes about 10-13hours before the CPU Leak hits 100% on one core. Already reset the env with `mv ~/.kde ~/.kde-old` and the issue has persisted. The only plugins running are: Task Manager, Application Launcher, Activities, System Tray Digital Clock OS / Kde Ver: [~]$ cat /etc/issue Fedora release 20 (Heisenbug) Kernel \r on an \m (\l) [~]$ plasma-desktop -version Qt: 4.8.6 KDE Development Platform: 4.12.5 Plasma Desktop Shell: 4.11.10
Hello, sorry for taking so long time until I have tested this: With a freshly created user it does not have this problem. Am 24.04.2014 um 14:12 schrieb Christoph Feck: > https://bugs.kde.org/show_bug.cgi?id=333653 > > Christoph Feck <christoph@maxiom.de> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Component|general |general > Version|Git |unspecified > Assignee|unassigned-bugs@kde.org |plasma-bugs@kde.org > Product|kde |plasma > > --- Comment #4 from Christoph Feck <christoph@maxiom.de> --- > Which version of kde-workspace are you using? > > Could you try removing some widgets to see which one causes the issue? Does it > also happen with a freshly created user account? >
I would like to confirm this problem. My system is exhibiting the exact same symptoms as reported by the other users here. It seems like something is provoking a resource leak in the plasma-desktop process. After about a day, its CPU utilization climbs to 100% with very high memory usage and the desktop becomes very sluggish and slow to respond. (Other applications are unaffected.) The problem can be fixed temporarily by restarting plasma-desktop as follows: $ kbuildsycoca4; kquitapp plasma-desktop; sleep 2; kstart plasma-desktop My system is Kubuntu 14.04.2 LTS, upgraded from Kubuntu 12.04. tabernacle:~$ plasma-desktop -version Qt: 4.8.6 KDE Development Platform: 4.13.3 Plasma Desktop Shell: 4.11.11 Just like for ndmuir above, the problem persisted after starting with a fresh KDE environment. (Log out, `mv ~/.kde ~/.kde-old; rm -r /var/tmp/kdecache-<username>`.) I have just the one standard panel with the following widgets: Application Launcher Activities Desktop Switcher/Pager Task Manager Show Desktop System Tray CPU Monitor (v1.0) Digital Clock Is there anything else I can do to help pinpoint the cause? Is there any other saved state beside ~/.kde and /var/tmp/kde-cache-<username> that should be cleared to start fresh? I would be happy to provide you with any other configuration information if it might help. Thanks!
Just an update to say that I have made two minor changes to my desktop configuration after which I no longer seem to be seeing the problem (after >24 hours): 1. Removed Activies widget from plasma panel. 2. Disabled the "Blur" effect in System Settings -> Desktop Effects Of the two, I strongly suspect it was related to the latter (#2) since I was inspired to make the change by this post: KDE: Unresponsive/slow/frozen plasma panel - http://forums.fedoraforum.org/showthread.php?t=284387 Perhaps it's video driver related as the author at the link above suggests? Here is my video hardware as reported by `lspci`: 01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] Here is some more info excerpted from my /var/log/Xorg.0.log file (which I will attach): [382058.304] X.Org X Server 1.15.1 Release Date: 2014-04-13 ... [382058.443] (--) RADEON(0): Chipset: "ATI Radeon 3000 Graphics" (ChipID = 0x9616) I hope this info be useful to someone! Thanks!
Created attachment 92107 [details] X.org X Server log showing graphics hardware details
Which composition backend are you using? Pleas try to change the backend and see if there are any difference.
Hello! This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham