https://bugs.kde.org/show_bug.cgi?id=488843

Zamundaaa <xaver.h...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
                   |ma/kwin/-/commit/457b3a47ff |ma/kwin/-/commit/7b8f24698f
                   |e91b335ab18170cfb830d35217b |797143531f0d5723cc6c263b917
                   |9a8                         |5e8

--- Comment #40 from Zamundaaa <xaver.h...@gmail.com> ---
Git commit 7b8f24698f797143531f0d5723cc6c263b9175e8 by Xaver Hugl.
Committed on 26/07/2024 at 13:10.
Pushed by zamundaaa into branch 'Plasma/6.1'.

core/renderloop: don't move the target presentation timestamp back when
rescheduling

Re-doing the frame scheduling for an already scheduled composite cycle was
meant to
adjust to small timing changes in the presentation timestamp, but if the
expected
compositing time was close to vblank, it could happen that this would instead
move
the target presentation timestamp and effectively drop a frame.

To fix that, this commit makes the presentation timestamp be adjusted only to
be more
accurate, but still target the same vblank interval.

M  +11   -1    src/core/renderloop.cpp

https://invent.kde.org/plasma/kwin/-/commit/7b8f24698f797143531f0d5723cc6c263b9175e8

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to