<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - KDE Konsole very slow scrolling with TearFree and QT graphics system native" href="https://bugs.freedesktop.org/show_bug.cgi?id=77436#c36">Comment # 36</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - 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>the same with Icewm. i dont know if this problem deserve so much attention. QT doesn't use xrender by default anyway. Of course it is surprising how application produces frames without caring about whether they was drawn on screen and no proper frame skipping takes place. I believe that app always must try to show its actual state. The most surprising thing for me is - where all this queue of frames to be drawn is stored. in 2. TearFree false, kwin Xrender mode it takes seconds or even dozens of second to catch up to actual state. And all the frames are drawn. Where was they stored .. so much data. Offtopic: i've noticed sna performance regression with 3.14 kernel. from 1.18s in gtkperf to 1.88s. should i report bug or this is smth in OpenSuSE?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>