[Wayland-bugs] [Bug 769835] On Wayland, application containing GtkGLArea stops responding if it's not on current workspace
gtk+ (GNOME Bugzilla)
bugzilla at gnome.org
Thu Dec 1 13:39:37 UTC 2016
https://bugzilla.gnome.org/show_bug.cgi?id=769835
Jonas Ådahl <jadahl at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rob at robster.org.uk,
| |wayland-bugs at lists.freedesk
| |top.org
Component|wayland |Backend: Wayland
Assignee|mutter-maint at gnome.bugs |gtk-bugs at gtk.org
Product|mutter |gtk+
QA Contact|mutter-maint at gnome.bugs |gtk-bugs at gtk.org
--- Comment #9 from Jonas Ådahl <jadahl at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-bugs/attachments/20161201/f290de35/attachment.html>
More information about the wayland-bugs
mailing list