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

List:       kde-bugs-dist
Subject:    [kwin] [Bug 343551] Kwin hangs, stops drawing the screen and starts using 100% cpu inside nvidia-glc
From:       Thomas Lübking <thomas.luebking () gmail ! com>
Date:       2015-02-19 14:21:03
Message-ID: bug-343551-17878-iWdX0DSUEk () http ! bugs ! kde ! org/
[Download RAW message or body]

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

--- Comment #35 from Thomas Lübking <thomas.luebking@gmail.com> ---
(In reply to Fredrik Höglund from comment #32)
> What glDeleteSync() is clearly waiting for is for the fence to become signaled

(excuse my stupidity)
Is this any "clearly" beyond hindsight?
From out of all options, I considered this to be the least reasonable one
(would that mean the driver is in pre-emptive waiting condition - and what
would be the runtime implications for windows that never trigger the fence?)

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