Bug 315879

Summary:	Present Windows is slow and hangs/freezes for seconds during interaction
Product:	[Plasma] kwin	Reporter:	Niels Myrtue <nielsgm>
Component:	effects-window-management	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	4.10.0
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Niels Myrtue 2013-02-27 23:36:20 UTC

I've begun to experience an issue where the Present Windows feature will hang/freeze, sometimes for more than a second when, I interact with windows in the grid. It doesn't seem to matter how many or few windows are displayed. If i move the cursor between windows, the animation is very choppy to the point of not updating the grid at all.

It started to happen after my last system upgrade and could be due to Mesa 9.1.


Reproducible: Always

Steps to Reproduce:
1. Activate Present Windows by any means be it hotkey, moving cursor to top-left corner or through the icon-only task manager
2. Move the cursor between windows
3. Click on a window

Actual Results:  
The animation hangs/freezes frequently during any interaction, sometimes for more than a second

Expected Results:  
The animation should be smooth and clicking on windows should not cause a delay

Graphics card: Intel Ivy Bridge integrated: HD4000

relevant Arch packages:
mesa 9.1-2 (Just upgraded)
intel-dri 9.1-2
xf86-video-intel 2.21.3-1
kde 4.10.0-1

Comment 1 Thomas Lübking 2013-02-27 23:43:28 UTC

Probably bug #313613 - try to set the scale method to "smooth" (kcmshell4 kwincompositing, 3rd tab) and report back.

Comment 2 Niels Myrtue 2013-02-28 00:02:43 UTC

Setting the scaling method to smooth did the job. Animation is now smooth again. Thanks!
I gather from the other bug report that it is in fact a problem with Mesa 9.1?

Comment 3 Thomas Lübking 2013-02-28 00:44:11 UTC

Thanks for the report.
Yes, at least the issue is exposed by Mesa 9.1 - we yet don't know what the precise issue is, though.

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