<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Awful screen tearing in a separate X server with DRI3" href="https://bugs.freedesktop.org/show_bug.cgi?id=97957#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Awful screen tearing in a separate X server with DRI3" href="https://bugs.freedesktop.org/show_bug.cgi?id=97957">bug 97957</a> from <a class="email" href="mailto:thellstrom@vmware.com" title="Thomas Hellström <thellstrom@vmware.com>"> Thomas Hellström</a> <pre>(In reply to Fredrik Höglund from <a href="show_bug.cgi?id=97957#c15">comment #15</a>) > (In reply to Thomas Hellström from <a href="show_bug.cgi?id=97957#c13">comment #13</a>) > > It sounds to me like a back- to back SwapBuffers() is an application bug. > > The back buffer content is undefined after a SwapBuffers(). > > It is not undefined when the implementation supports EXT_buffer_age. Well it may be for some buffers. Whether or not the app uses EXT_buffer_age correctly in this case doesn't really matter as there are apps out there that most certainly don't. Perhaps we can use a driconf option for such apps to restrict available swap methods. But most importantly there is a mesa dri3 bug here. And looking closer at the code the glx/dri implementation of GLX_OML_swap_method appears utterly broken, so it will take some time to fix.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>