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 569366 - Metacity do unneeded expose events when desktop switching
Metacity do unneeded expose events when desktop switching
Status: RESOLVED OBSOLETE
Product: metacity
Classification: Other
Component: general
2.24.x
Other All
: Normal minor
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2009-01-27 17:24 UTC by Guillaume Bouchard
Modified: 2020-11-06 20:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Guillaume Bouchard 2009-01-27 17:24:55 UTC
When switching between virtual desktops, metacity send an expose event to all applications from the new desktop resulting on a short lag, even if the compositor is activated.

Other information:
The lag is ~1 sec. on my 400 Mhz laptop, shorter but visible on my "powerfull" (1.6 Ghz with nice 3d card) desktop computer.

- It is not "nice"
- It takes lot of time when switching from desktop 1 to desktop 10 one by one.
- It use CPU to redraw all the windows, so consume more power.

I think it's a bit related with Bug 504729.

Now, it's the last remaining problem that block me to use the compositor on my computers.
Comment 1 Travis Watkins 2009-01-28 05:11:49 UTC
Would not unmapping windows on workspace switch solve this problem? It is my understanding that the clutter version of metacity already does it this way so it's probably safe to do in metacity as well. Would cost some memory though.
Comment 2 André Klapper 2020-11-06 20:05:35 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/metacity/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.