https://bugs.kde.org/show_bug.cgi?id=431509
Vlad Zahorodnii <vlad.zahorod...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
Latest Commit| |https://invent.kde.org/plas
| |ma/kwin/commit/b5a1eba2779b
| |06715508365c6e2b86017151cef
| |0
--- Comment #41 from Vlad Zahorodnii <vlad.zahorod...@kde.org> ---
Git commit b5a1eba2779b06715508365c6e2b86017151cef0 by Vlad Zahorodnii.
Committed on 14/01/2021 at 18:45.
Pushed by vladz into branch 'master'.
Properly schedule repaints with premature presentation timestamps
The last presentation timestamp might be in the future by a couple of
hundred microseconds.
This may break timestamp aligning code because it assumes that the
last presentation timestamp is less or equal to the current time.
In order to properly handle this case, we have to first compute the
next expected presentation timestamp by advancing the last presentation
timestamp by the amount of vblank interval. If that fails, we can safely
resort to aligning timestamps.
Related: bug 431449
M +5 -2 renderloop.cpp
https://invent.kde.org/plasma/kwin/commit/b5a1eba2779b06715508365c6e2b86017151cef0
--
You are receiving this mail because:
You are watching all bug changes.
