[Bug 158349] New: High CPU usage by X and plasma processes when moving mouse cursor near the plasmoid edge

Andrey Melentyev rikz at yandex.ru
Sun Feb 24 19:39:49 CET 2008


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=158349         
           Summary: High CPU usage by X and plasma processes when moving
                    mouse cursor near the plasmoid edge
           Product: plasma
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: panel-devel kde org
        ReportedBy: rikz yandex ru


Version:            (using Devel)
Installed from:    Compiled sources
Compiler:          gcc-4.2.3 
OS:                Linux

Currently I have three plasmoids on the desktop (except panel and plasmoids on the panel): Dictionary, Notes, Picture frame. They are locked using RMB - Lock Widgets. Desktop effects are completely disabled.

1) When mouse cursor crosses the plasmoid border, CPU usage for X proccess grows up to 50-60% (which is too high, I think) and plasma proccess consumes 5-10% of CPU. 
2) If I just move the mouse around the wallpaper, X uses ~10% of CPU and plasma less than 1%. 
3) If I move mouse cursor above the content of one of the plasmoids (not crossing the plasmoid's border), CPU usage is 5-10% for each process.

2 and 3 cases are ok, but the first case seems suspicious to me. When widgets are locked, if I point mouse cursor at them, nothing happens. I mean, there's no slowly-appearing transparent border, so X doesn't do any real work and CPU usage by X proccess must not be high. 

Here's a screenshot: http://img178.imageshack.us/img178/9738/46773394ml4.png - I was continuously moving mouse cursor from Notes plasmoid to the wallpaper.

Sorry for my bad language knowledge and explanation. I will provide any additional information if needed.


More information about the Panel-devel mailing list