[Bug 91036] TearFree option bugs

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jun 22 16:44:10 PDT 2015


https://bugs.freedesktop.org/show_bug.cgi?id=91036

--- Comment #26 from Kevin Mitchell <kevmitch at gmail.com> ---
> 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?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150622/f0f014c9/attachment.html>


More information about the intel-gfx-bugs mailing list