Version: (using Devel) Compiler: gcc 4.3.2 / gcc 4.4 OS: Linux Installed from: Compiled sources When I keep moving the mouse over plasma, plasma-desktop eats up to 40% cpu. Doesn't look quite normal to me but I don't see any special reason for this.
- What is your KDE version (svn revision/branch) ? - Did you recognize some pattern in the CPU usage? (did you tried only moving the mouse over certaing widgets?). Thanks
Last update was some days ago. When I start moving the mouse (fast) the cpu usage goes up and stays there until I stop moving. At the moment (after the last update) I only get it to ~25% (external mouse) and 13% (touchpad; I don't know if the movement using the touchpad is so much slower). Tried moving the mouse over a "fullscreen" folder view, a very big clock or the taskbar which results in the same.
btw. forgot to mention that I'm using the sources directly from trunk.
So, you are moving the mouse over the widgets on the desktop, does this also happens in the panel ? Is your version updated? Thanks
It is enough to move the mouse over the desktop (there don't have to be any widgets, higher cpu usage when moving the mouse faster). Same with the panel. I am updating kde at least every few weeks. But I don't know if this is completely plasma related. For me the same happens when moving the mouse over Firefox, but not with e.g. dolphin..
firefox is unrelated (it just has crappy updates too ;) .. no, this is a regression in the 4.3 codebase where exiting an plasmoid causes a full containment repaint. i need to talk with the trolls about this. *sigh*
Hi, I use KDE 4.3 RC1 (aka 4.25 ) from the ubuntu experimental Repository and I also experience this bug. Top shows me ~75% CPU Usage when moving the Mouse over Plasma, no difference where ( panel, desktop...). When I move it over the xterm, Plasma only uses 8% CPU ( which is FAR too much, but that should be another bug ). Anything new on this issue?
"when moving the Mouse over Plasma" moving the mouse _where_ over plasma? in and out of a widget? around on the wallpaper? the details matter immensely. "Plasma only uses 8% CPU" and if you aren't moving the mouse? what wallpaper and widgets are you using?
Hi, to be precise: System is a Dell XPS M1330 1,8Ghz Core 2 Duo running at 800Mhz ( Speedstep ) Open Windows: Xterm, about 1/4 of the screen Plasma Widgets: Program Folder on the Desktop, 2 Panels ( top, right ), task manager (list of all minimized windows ) in the top panel, network manager, workspace switcher, K-Menu, date and time, "folder quicklaunch", lock button in the right panel I'm sorry that I don't know the english names of the widgets as I use a German KDE. Wallpaper is a standard 1280x800 ( screen resolution ) PNG, I will try without later. All CPU Usages reported by top for the process plasma-desktop: Doing _nothing_, Mouse is on the Wallpaper: 8% CPU Usage Moving the Mouse with ~0,3m/s over the Wallpaper gives 60%-70% CPU Usage Moving the Mouse at same speed at the top edge of the screen e.g. over the top panel: 60-70% CPU Usage Moving the Mouse at same speed over xterm: 10% CPU Usage For Comparison: E17, xterm Open, doing nothing: 1% CPU Usage by process enlightenment, moving the Mouse: about 8% CPU. If there is some easy debugging I can do ( maybe without compiling whole KDE ) I would be glad to help.
Does this still occur?
I guess that I still have this problem but at least for me it apparently got better. CPU usage for plasma-desktop when I keep moving the mouse is about 10% (using folder view as my activity type). X goes up to 15-20% (may also be caused by the nvidia driver). Currently using 8.3.85 and Qt 4.6.9999 (qt-copy).
Okay. I can't do anything about this, though. I was just confirming (as part of BugWeek) if this had somehow "fixed itself". :)
Can you reproduce using KDE 4.4.4 or 4.5beta?
At least I can't reproduce any noticeable high cpu usage at the moment. Currently using: KDE 4.4.4 (few custom patches to fix some compile errors with Qt 4.7) Qt 4.7 from svn (probably some weeks old) and raster graphicssystem
so it varies between Qt versions, probably also which graphics backend ... typical variations related to issues lower in the stack. not much we can do about this further in plasma code afiact.