[Bug 85665] New: mpv hits BadDrawable on vaapi/opengl interop teardown

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 85665
           Summary: mpv hits BadDrawable on vaapi/opengl interop teardown
           Product: xorg
           Version: git
          Hardware: Other
               URL: https://github.com/mpv-player/mpv/issues/1211
                OS: Linux (All)
            Status: NEW
          Keywords: bisected
          Severity: normal
          Priority: medium
         Component: Driver/intel
          Assignee: chris at chris-wilson.co.uk
          Reporter: kevmitch at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org

I have bisected the appearence of this bug down to
    xf86-video-intel:d8eb87f84f88ad2df42c6fed1d93df76589a14e3
    Author: Chris Wilson <chris at chris-wilson.co.uk>
    Date:   Thu May 8 16:25:32 2014 +0100

        sna: Add support for DRI3

        Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>


Hardware: Mesa DRI Intel(R) Ivybridge Mobile

After this commit, running mpv-player from git master (though all tested
versions show the same symptom) with the following command

    mpv/build/mpv --no-config --hwdec=vaapi --vo=opengl --msg-level=all=trace
<h264file>

will result in the following output right before the player exits (either
because of regular end of file or the user quitting the program with "q").

    .
    .
    .
    Exiting... (Quit)
    [osc] Exiting...
    [ao/alsa] draining...
    [ao/alsa] uninit: pcm closed
    [input] release all
    [vo/opengl/x11] Enabling screensaver.
    [vo/opengl/x11] X11 error: BadDrawable (invalid Pixmap or Window parameter)
    [vo/opengl/x11] Type: 0, display: 0x7f1a9825d0f0, resourceid: 4a0000d,
serial: 141
    [vo/opengl/x11] Error code: 9, request code: 9a, minor code: 4
    [vo/opengl/x11] uninit ...

No other ill effects are observed by the user. I tried narrowing down the error
within the mpv code, but it appears to be happening on essentially
random/unrelated X calls (i.e., xss_suspend, or XDefineCursor depending on
whehter the --no-stop-screensaver is added) likely because the x connection is
asyncronous.

This behaviour is only observed with the above combination of vaapi hardware
decoding with opengl interop output (i.e, none of "--hwdec=vaapi --vo=vaapi",
"--hwdec=vaapi-copy --vo=opengl", or "--hwdec=no --vo=opengl" exhibit this
problem).

I have linked the mpv bug report in the URL for this bug.

-- 
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/20141031/135d6d1b/attachment.html>