Version: unspecified (using KDE 4.4.4) OS: Linux I enabled the CPU graph and the Network graph. system starts up ok (no odd cpu usage) then slowly the cpu usage goes up. this is shown in the widget and in the system monitor. widget shows usage over last XX minutes. this *might* be related to the time period the graph is showing (since i started it) as the cpu usage appears to ramp until it hits either 22% or 50% (i have dual core). removing these widgets cures problem, but suse dont have any activity indicators for Network so i would like to use them. I left the Network one on only and went away for a while. came back and it was steady at 33%(with Br0 and eth0). i left the CPU one on only and it was 12%. these readings are of Xorg in system monitor. (GREEN SUSE LOGO > applications > system > monitor> system monitor, this is not the system monitor widget - you may want to change some names as there is three different "system monitor"s written in these brackets!!!) Do note, this could be a problem with Xorg. Reproducible: Always Steps to Reproduce: this did interfere with my other bug reports until i discovered it. Actual Results: sluggish computer. Severity: I wish i could choose higher than Normal as this is really an "important" one, there is no crashing or dataloss. another level could be "annoyance" as that wouldnt be a bug.
i have a triple monitor setup using two video cards. moving to the other card does not fix problem.
using SUSE 11.3
i can confirm this with the network monitor; so something in that stack is creating problems: the graph widget, the monitor plasmoid, the systemmonitor dataengine.
*** Bug 248540 has been marked as a duplicate of this bug. ***
Can all reporters please post the qt version they are using + graphics driver and its version? For me it is NOT reproduceable on qt 4.6.3 with intel driver 2.12
System: Kubuntu 10.4 KDE 4.5.1 Qt 4.6.2-0ubuntu5 card: VGA compatible controller: ATI Technologies Inc RC410 [Radeon Xpress 200] driver: radeon 1:6.13.0-1ubuntu5 hope this may help :)
i do have two video cards, three screens. and placing widget on any screen will produce problem. i have the distinct feeling that when fixed it make my computer more responsive in other programs also. SUSE 11.3 KDE 4.4.4 package: libqt4 installed version 4.6.3-1.5 (i can get version 4.6.3-2.1.1) will speed up SUSE alot. (from Xorg.0.log) (--) PCI: (0:1:0:0) 10de:0091:10de:02c2 nVidia Corporation G70 [GeForce 7800 GTX] (--) PCI:*(0:3:0:0) 1002:5e4d:0000:1e4d ATI Technologies Inc RV410 [Radeon X700 (PCIE)] (II) LoadModule: "radeon" (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so (II) Module radeon: vendor="X.Org Foundation" compiled for 1.8.0, module version = 6.13.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 7.0 (II) LoadModule: "nvidia" (II) Loading /usr/lib/xorg/modules/updates/drivers/nvidia_drv.so (II) Module nvidia: vendor="NVIDIA Corporation" compiled for 4.0.2, module version = 1.0.0 Module class: X.Org Video Driver
The bug still exists. Am having this problem on Arch Linux, KDE 4.6.
Please report at least your Qt version, graphics card, graphics driver (version) and xorg-server version.
I can confirm this bug with my Arch Linux system too. - Intel Core Duo T2300 - ATI Mobility Radeon X1400 - OpenGL vendor string: X.Org R300 Project - OpenGL renderer string: Gallium 0.4 on ATI RV515 - OpenGL version string: 2.1 Mesa 7.10.1-devel - OpenGL shading language version string: 1.20 - Kernel 2.6.37 - Qt 4.7.1 - KDE 4.6.0 - Desktop effects either on or off - System monitor widget with CPU, RAM, hard disk, temperature and network With the widget, Plasma and X start to take over my CPU until my computer becomes totally unresponsive, then CPU usage goes down. Actually, CPU usage goes repeatedly up and down. After removing the system monitor widget my computer is contantly responsive.
I did some tests with the system monitor widget. First, I tried the temperature and RAM monitors. Plasma kept a steady 1% cpu usage, apparently without impacts on X. As soon as I added the CPU monitor, my computer started to slowdown until it almost froze. CPU usage of Plasma-desktop and X went nuts. So I think the network monitor is not the only cause of the problem.
Sorry; here ya go: - AMD Athalon II X2 245 - Nvidia Geforce 7900 GS - Qt 4.7.1 - KDE 4.6.0 - Kernel 2.6.37 - xorg-server 1.9.4 As Victor pointed out, it ain't just the network monitor. The CPU monitor by itself will do it as well.
Same problem here. Intel 3 GHz Core Duo, Opensuse 11.3, KDE 4.6, Qt 4.7.1, Xorg 7.5-11.3, Nvidia 8xxx running 260.19.29_k2.6.34.0_12-21.1 with 2 Monitors When the System is running for > 1 day, Xorg CPU goes up to around 80% (and stays there), without obvious reason. Removed Plasma Network Monitor (without reboot or logout), Xorg CPU dropped down to ~ 30%, and even while wiggling a window will stay < 40 %. (Note: This level (30%) is probably explained by the gazillion of windows I have open, konperor, dolphin, opera, skype, psi+ etc, so that's OK, the system is not so very sluggish any more, I can use it again :) ) Still running the plasma widgets yaWP, Server Status, Translatoid, Hardware Temperature, and in the Panel the System Load Viewer. The system is still somewhat sluggish, so there might be another widget to remove, unfortunately. But removing the Network Monitor widget had a huge effect already.
Addon to #13: Removing the plasma widgets Translatoid, Hardware Temperature, and in the Panel the System Load Viewer seems not to further improve / influence the Xorg CPU load.
Addon to #13 and 14: After upgrading Xorg to 7.6 and Nvidia to 260.19.36 the system was (still without Plasma Network Monitor) fast and responsive, a pleasure to work with. Xorg CPU <10% - 20%, and even with a lot of activity rarely reaching 80%, and the system never feels sluggish. Then I added the Plasma Network Monitor again. CPU of Xorg went up again (within a couple of hours) to 60-80%, the system was sluggish again :( Removed Plasma Network Monitor and Xorg CPU dropped back to <10% - 20% :)
Addon to #13 and 14 and 15: Adding the Hardware Temperature Widget has a similar effect, but much smaller. After adding the Hardware Temperature Widget Xorg CPU went up to ~40 %, the system was feeling somewhat somewhat sluggish. Removed Plasma Hardware Temperature Widget again and Xorg CPU dropped back to ~20% :)
Addon to #13-#16: 1) Xorg server is 7.6_1.9.3-128.1 2) Adding the System Load Viewer Widget in the Panel seems not to have a significant effect. I hope this information helps to find a solution for this problem. Before I found this bug and removed the Plasma Network Monitor Widget the system was so sluggish that it was a pain to use, when working under time pressure the sluggishness and the delayed reaction on mouseclicks almost drove me crazy. When searching then all I found was kwin bashing, which made me sad to see. I'm sure that currently kwin gets a lot of heat for this bug here, which seems to be not related to kwin at all. Therefore I suggest to give this bug some priority, fixing it will take some (undeserved) heat off of the kwin developer.
have a look at the update interval in the config and monitor visual updates with the "show paint" effect plugin of kwin.
I've confirmed the following widgets to cause xorg to use very high cpu in 4.5.5: Network Monitor CPU Monitor Memory Monitor It seems that any widget that draws a graph causes the CPU to rise steadily over one to six hours until xorg starts using the majority of the CPU. The System Load Viewer seems to be OK, as stated, but I find that it still has problems. When another process is causing a lot of activity, the system load viewer does seem to add 10 percent or so. The graph plasmoids have caused complete system lockups for periods of a minute or so when trying to play a video in mplayer. System Load Viewer causes enough extra load that when, for example, virtualbox is booting in another window, mplayer drops frames. Without it, mplayer is unaffected. In this case, however, things go back to normal when the load on the system decreases, while the cpu from the graph widgets is never released. libqt4 4.4.7, kde 4.5.5, nvidia drivers 260.19 and 270.29. Ksysguard draws more frequently updated graphs without any noticeable effect. The previous version of KDE I used, 4.2 from Kubuntu 9.10, had no problem with any of these widgets, with the 260 nvidia drivers.
> Ksysguard draws more frequently updated graphs without any noticeable effect. Have you verified this using eg. the show paint plugin, because the plasmoid could repaint "immediately" w/o causing any _visual_ update. (Ie. there's a repaint, but you don't see it because the content remains)
i have switched back to SUSE 11.2 it has KDE 4.3.1-5.6.3 and has no visible problems.
Same for me with Fedora 15 and CPU Usage widget running. Without the widget, no problem. With the widget, CPU ussage increases to 100% after about 20 hr. Using kmod-nvidia-2.6.38.7-30.fc15.x86_64-270.41.06-2.fc15.1.x86_64 and qt-4.7.2-8.fc15.x86_64 See also https://bugs.kde.org/show_bug.cgi?id=273214 and https://bugzilla.redhat.com/show_bug.cgi?id=710918
I only have the network manager widget running (of widgets that draw graphs). When I click on the widget in the tray and then click on the network interface (on the left) to see the graph, my CPU usage increases even after closing the widget again (without closing the interface graph first). I have same problem with slowly climbing CPU usage of the "plasma-desktop" process that might be related to that widget and its graph. It usually climbs over a day or so of use (lots of suspends) until it maxes out one core/thread...and then I reboot! (Fedora 15 64-bit, KDE 4.6.5, Intel HD 3000 SNB graphics)
I can confirm this bug.
*** Bug 248016 has been marked as a duplicate of this bug. ***
(In reply to comment #24) > I can confirm this bug. Witch which version? Is this still valid for KDE 4.8.3?
Hello! Plasma 4 was replaced by Plasma 5 four years ago by the KDE community. In that time we have made great strides in stability and functionality. We are closing all Plasma 4 bugs as most of them are no longer applicable to the new frameworks Plasma 5 is built upon. If you could, please re-test with the latest version of Plasma 5, and submit a new bug to "plasmashell" if you continue to have an issue. Thank you!