<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Severe tearing and display corrupting when using SNA" href="https://bugs.freedesktop.org/show_bug.cgi?id=110245#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Severe tearing and display corrupting when using SNA" href="https://bugs.freedesktop.org/show_bug.cgi?id=110245">bug 110245</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>It's just whether the corruption is apparent int the screenshots and if that corruption only occurs on the external outputs that is particularly of interest. If you don't see it in a screenshot (and that screenshot shows the remote output windows correctly) that implies the corruption is entering in ivo -> bumblebee path. We should be pageflipping on the internal screen, no matter what. That may still tear across between client rendering (if the client split his update into two requests and we perform a page flip in between), or it may tear in situations where we give the client direct access to the screen and require them to manage it through glXSwapBuffers (that should only impact DRI3 iirc). ivo doesn't try to avoid tearing on the external screens at all atm. It's a wishlist item along with using DRI3 to avoid the copies; at which point, xrandrproviders were meant to be the better solution. Nothing should have changed to make it any worse, though. Anyway, the immediate problems are tearing on the internal and corruption on the external?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>