Bug 243686 - KWin and XOrg slows down very much after time
Summary: KWin and XOrg slows down very much after time
Status: RESOLVED DUPLICATE of bug 234463
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 0.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-05 20:46 UTC by Unknown
Modified: 2010-07-05 22:42 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
NVIDIA bug report file containing everything from my system (52.97 KB, application/x-gzip)
2010-07-05 20:46 UTC, Unknown
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2010-07-05 20:46:11 UTC
Created attachment 48611 [details]
NVIDIA bug report file containing everything from my system

Version:           0.2 (using Devel) 
OS:                Linux

In KDE 4.5 RC 1, KWin and Xorg eat a whole core of my CPU after a time. Everything slows down noticeable. It happens randomly but needs some hour of uptime or a sleep-restore.

In that case every graphical function slows down (moving window, using plasma, loading pages in Opera, using file selector dialogue etc.).

If you can read, I can attach a perf log of kwin and Xorg.

Here, I attach an NVidia bug report.sh file, in that you can find everything related (I hope).

Reproducible: Sometimes
Comment 1 Thomas Lübking 2010-07-05 21:28:22 UTC
sounds like bug #234463

can you also please check that it's not related to the blur plugin?
do you use multiple monitors ("twinview")

"perf logs" as like a sysprof export can be of help (but the issue may be inside nvidias css driver blob, where you can't really read anything - function names seem encoded :-(
Comment 2 Unknown 2010-07-05 22:17:11 UTC
Yes, it seems, it's a duplicate.
I do have blur plugin enabled but not Twinview. I try to reproduce and monitor it with sysprof or perf.
Comment 3 Martin Flöser 2010-07-05 22:42:53 UTC

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