<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <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#c51">Comment # 51</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 <a class="email" href="mailto:absorbb@gmail.com" title="Ildar Nurislamov <absorbb@gmail.com>"> Ildar Nurislamov</a> <pre>Same story - with diablo it is hardly possible to achieve delay. I came out with different theory. what if Diablo actually makes everything slower (as it should). And Konsole manages to draw much less fps so frame buffers or queues (i don't know) doesn't overrun. Yes i have no idea how driver works. But behavior with TearFree disabled make me believe that there must be some queue somewhere and that this queue can be insanely long like few seconds of drawing at ~20fps (what i think is weird. before i though that there is tripple buffer and nothing more) Or maybe this is not frames queue in the driver but rather X protocol commands queue in the X server. And QT is the one who stupidly overwhelm server with commands without much care of produced result. QT doesn't use xrender backend by default. It may be abandoned and broken.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>