https://bugzilla.gnome.org/show_bug.cgi?id=775093
--- Comment #3 from Benjamin Berg <[email protected]> ---
So, I have learned that removing gdk_window_process_updates in VTE almost
solves this bug (but not entirely!).
Patrick was hitting it a lot in newer gnome-shell versions (with
maximize/unmaximize animation). Removing the call to gdk_window_process_udpates
fixes it in most cases, but the bug can still be triggered when
maximizing/unmaximizing quickly in a row.
So it seems like:
* Triggering might require a committed frame to be pending
* It can be triggered by updates happening outside of the frame clock
(which doesn't necessarily mean a frame is pending, just that we render
multiple times into the staging frame)
* It *might* be related to back-filling from an already committed buffer
(i.e. back-filling areas that were actually updated)
* Further partial updates will *not* cause the area to appear
* mutter will get multiple attach + damage rectangles
(attach for the same surface, damage needs to be aggregated)
Unfortunately, I have read over the back-filling code and I cannot think of any
corner case where it goes wrong. I am not that sure about the mutter side
though.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
wayland-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
