90aee21f20
If the presentation time isn't known, e.g. if the monitor is virtual and the actual presentation happens far away, the presentation time we actually received tends to be the time a frame was presented to the next layer, meaning practically immediately after painting. When scheduling another update after that, don't assume that if the next calculated update is not the immediate next update, schedule an update sooner, as that will in such cases always be true, meaning we ended up busy looping with constant frame updates being scheduled. Fix this by only triggering that logic if the last presentation time was actually vsync:ed. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3803> |
||
---|---|---|
.. | ||
clutter | ||
meson.build |