[mutter/wip/carlosg/xwayland-on-demand: 1/7] x11: Do not queue stack operation for guard window
- From: Carlos Garnacho <carlosg src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [mutter/wip/carlosg/xwayland-on-demand: 1/7] x11: Do not queue stack operation for guard window
- Date: Fri, 24 May 2019 21:48:16 +0000 (UTC)
commit cee62b8dd73115865faaa8717eb4782106596853
Author: Carlos Garnacho <carlosg gnome org>
Date: Fri May 24 23:27:40 2019 +0200
x11: Do not queue stack operation for guard window
In the case mutter is a x11 compositor, it doesn't matter much
since the stack tracker will go away soon. In the case this is a
wayland compositor with mandatory Xwayland, it matters even less
since the session would be shutting down in those paths.
But if this a wayland compositor that can start Xwayland on demand,
this is even harmful, as the MetaStackTracker should be cleared of
x11 windows at this moment, and we actually did right before dispose
on ::x11-display-closing.
src/x11/meta-x11-display.c | 10 ----------
1 file changed, 10 deletions(-)
---
diff --git a/src/x11/meta-x11-display.c b/src/x11/meta-x11-display.c
index fb979cd93..71658c55e 100644
--- a/src/x11/meta-x11-display.c
+++ b/src/x11/meta-x11-display.c
@@ -176,16 +176,6 @@ meta_x11_display_dispose (GObject *object)
{
MetaStackTracker *stack_tracker = x11_display->display->stack_tracker;
- if (stack_tracker)
- {
- unsigned long serial;
-
- serial = XNextRequest (x11_display->xdisplay);
- meta_stack_tracker_record_remove (stack_tracker,
- x11_display->guard_window,
- serial);
- }
-
XUnmapWindow (x11_display->xdisplay, x11_display->guard_window);
XDestroyWindow (x11_display->xdisplay, x11_display->guard_window);
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]