<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - TearFree option bugs" href="https://bugs.freedesktop.org/show_bug.cgi?id=91036#c26">Comment # 26</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - TearFree option bugs" href="https://bugs.freedesktop.org/show_bug.cgi?id=91036">bug 91036</a> from <a class="email" href="mailto:kevmitch@gmail.com" title="Kevin Mitchell <kevmitch@gmail.com>"> Kevin Mitchell</a> <pre>> Tearing is expected if either the application requests tearing, or is too > slow to maintain the requested framerate (i.e. if it misses a frame, the > next frame is presented as soon as possible without synchronisation, the > technique is called adaptive vsync and is meant to help reduce jitter). Is there a way for the application to know programmatically when this happens? > > [vo/opengl/x11] X11 error: BadDrawable (invalid Pixmap or Window parameter) > > That's a distinct bug, it's generated by the core layer. There is one known > issue involving DRI2/DRI3 interop in mpv that generates that error, bug > 85665. I've just updated that one. I'm no longer seeing that problem likely as the result of a kernel or xserver update. That was also vaapi hardware-decoding specific, whereas the above described tests have hardware decoding disabled. > Ultimately I need to have a look at your Xorg.0.log to see which class of > errors you are likely seeing. standby will post later tonight. So I should open a separate bug for this?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>