After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 577319 - Alt+Tab window changes are (very) slow
Alt+Tab window changes are (very) slow
Status: RESOLVED DUPLICATE of bug 504729
Product: metacity
Classification: Other
Component: Iain's compositor
2.26.x
Other All
: Normal minor
: ---
Assigned To: Metacity compositor maintainers
Metacity compositor maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-30 15:30 UTC by Michael Trausch
Modified: 2012-12-16 14:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Michael Trausch 2009-03-30 15:30:56 UTC
Please describe the problem:
When compositing is enabled in Metacity, the Alt+Tab behavior is excessively slow (around half a second for just simple window switching, about the same to display the window switcher if I want to move around to another window other than the last one I used).

This is on NVIDIA hardware; compiz works pretty well on it, but I didn't want the overhead of all of its stuff.  I just wanted transparent terminals.  :-)

Steps to reproduce:
Enable compositing in metacity, and alt-tab to another window.

Actual results:
There is about a half-second delay in the window switcher's appearance and behavior.

Expected results:
The delay should not be noticeable, such as when compositing in metacity is not enabled.

Does this happen every time?
Yes.

Other information:
Comment 1 Matt Johnston 2009-05-14 02:29:03 UTC
Confirming here with (fedora 10's) metacity 2.25.55, xorg 1.5.3, nvidia 180.51.
Comment 2 Josh Bowman 2010-09-30 02:14:49 UTC
This is a duplicate of Bug 504729
Comment 3 Stéphane Démurget 2012-12-16 14:25:31 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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