[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kwin] [Bug 351118] composited mpv fullscreen video induces a GPU reset
From:       Thomas Lübking <thomas.luebking () gmail ! com>
Date:       2015-08-09 13:35:51
Message-ID: bug-351118-17878-xsZdRGXVyZ () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=351118

Thomas Lübking <thomas.luebking@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|effects-various             |compositing
              Flags|                            |NVIDIA+
            Summary|mpv fullscreen causes       |composited mpv fullscreen
                   |effects to not respond      |video induces a GPU reset

--- Comment #2 from Thomas Lübking <thomas.luebking@gmail.com> ---
That's actually no bug (in KWin) - everything acts as expected :-P

When you set mpv fullscreen, for some™ reason, the nvidia driver starts to
hang. KWin detects that and restarts the compositor.

The only question is *why* fullscreen mpv AND kwin compositing makes the nvidia
driver burp.

I've some suspicions here, but let's see ;-)

a) please dump "qdbus org.kde.KWin /KWin supportInformation" before *and* after
the hang (and compositor restart)
b) attach /var/log/Xorg.0.log *after* the reset
c) attach "dmesg | tail -100" (right) *after* the reset
d) attach "dmesg | grep NVRM" *after* the reset

Please check the output of mpv, notably what video output (vdpau? opengl?) is
used.

----
Suspending redirection for fullscreen windows is not known to cause trouble on
nvidia - the unnamed child here is intel; and we meanwhile forcefully disable
the feature on intel chips because of the daily bugreports ;-)
It's left as a general warning (and because ppl. belive it gains them much
performance, what's no more true since ages. Suspending the compositor
altogether does. Just not redirecting one window has little impact in this
regard)

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]