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

--- Comment #12 from Thomas L=C3=BCbking <thomas.luebking@gmail.com> ---
The cpu load can happen in the kernel, but the (assumed, we should check th=
at
next year) false positive detection of triple buffering as well as triple
buffering not resolving the issue alone (it does show up as active in
/var/log/Xorg.0.log, does it?) is indeed suspicious.
Could be that the refreshrate/maxfps is misdetected/overridden, we should c=
heck
for that as well ... next year ;-)

The core problem from our side (default yielding strategy causing "trouble=
=E2=84=A2"
for the nvidia blob) is however the same.

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