Bug 186192 - Wobbly windows high cpu usage
Summary: Wobbly windows high cpu usage
Status: RESOLVED DUPLICATE of bug 189999
Alias: None
Product: kwin
Classification: Plasma
Component: effects-various (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-05 09:58 UTC by Yves Glodt
Modified: 2011-03-09 20:22 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot of problem (153.04 KB, image/jpeg)
2009-03-05 09:59 UTC, Yves Glodt
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yves Glodt 2009-03-05 09:58:19 UTC
Version:           4.2.1 (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

I have set up the Translucency effect to make the windows a bit translucent while they are moved, this is hot, especially in combination with wobbly windows.

Now my complain: :-)

With this setup, just clicking the title-bar of the window, without actually moving it, makes cpu usage of kwin and xorg go high!

(To about 60-70% on a 3 year old laptop with free ati driver on jaunty, and to about 40% on a 2 month old laptop with fglrx on intrepid)
Comment 1 Yves Glodt 2009-03-05 09:59:20 UTC
Created attachment 31791 [details]
Screenshot of problem

While taking this screenshot I was actually just clicking and holding the click of the dolphin title-bar.
Comment 2 lucas 2009-03-05 10:54:23 UTC
Problem is actually caused by wobbly windows and it's the common repaint-loop bug. Having translucent windows enabled or disabled doesn't change anything.
Comment 3 Yves Glodt 2009-03-05 11:17:42 UTC
Indeed, I just tried to deactivate wobbly and the phenomenon disappears.
Comment 4 Michael Leupold 2010-10-10 18:35:01 UTC
Not specific to ATI drivers actually. I can reproduce using my GeForce as well (on trunk r1184315).
Comment 5 Martin Flöser 2011-03-09 20:22:02 UTC
situation should have improved with 4.6, but root cause is bug #189999 - therefore duplicate

*** This bug has been marked as a duplicate of bug 189999 ***