<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - KDE Konsole very slow scrolling with TearFree and QT graphics system native"
href="https://bugs.freedesktop.org/show_bug.cgi?id=77436#c29">Comment # 29</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - KDE Konsole very slow scrolling with TearFree and QT graphics system native"
href="https://bugs.freedesktop.org/show_bug.cgi?id=77436">bug 77436</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=77436#c28">comment #28</a>)
<span class="quote">> Screen still stops refreshing. Mouse cursor moves fine and CPU load looks ok
> most of the time. But everything is still as laggy as before.</span >
Good. That is actually what I expect. We haven't done anything to prevent the
backlog, so eventually we have to service all that rendering debt and stop
processing new commands. However, whereas previously that happened at an
unexpected point and blocked the Xserver, it now happens more or less under our
control and we allow X to continue processing requests and update the cursor.
Thanks for all your help so far, I need to think how we can get a clear picture
of what is causing the backlog.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>