https://bugzilla.gnome.org/show_bug.cgi?id=769835

Jonas Ådahl <jad...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |r...@robster.org.uk,
                   |                            |wayland-bugs@lists.freedesk
                   |                            |top.org
          Component|wayland                     |Backend: Wayland
           Assignee|mutter-ma...@gnome.bugs     |gtk-b...@gtk.org
            Product|mutter                      |gtk+
         QA Contact|mutter-ma...@gnome.bugs     |gtk-b...@gtk.org

--- Comment #9 from Jonas Ådahl <jad...@gmail.com> ---
(moving back to gtk+ since this is about frame throttling getting away of
unrelated IO)

I think that, for whatever reason a frame is scheduled (be it because some
focus-out animation or an application deliberately asking for it for whatever
reason), we should still handle the situation where we actually don't want to
paint because of the vsync throttling.

As far as I can see, we use _gdk_frame_clock_freeze() and
_gdk_frame_clock_thaw() to do the throttling, but maybe what we really should
do is gdk_window_freeze_updates()/gdk_window_thaw_updates()? We handle those
here and there in gdkwindow-wayland.c (the checking of
window->update_freeze_count).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

Reply via email to