https://bugs.kde.org/show_bug.cgi?id=358646
Bug ID: 358646
Summary: Rendering breaks if Triple Buffer detection gives NOT
available
Product: kwin
Version: git master
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: glx
Assignee: kwin-bugs-n...@kde.org
Reporter: mgraess...@kde.org
Flags: Intel+
>From Time to time my KWin (Intel Ivybridge) reports:
Triple buffering detection: "NOT available" - Mean block time: 1.25074 ms
>From that time on the rendering is completely broken and restarting the
compositor fixes it. The next triple buffer detection might work again. E.g.
the current session has:
KWin::SwapProfiler::end: Triple buffering detection: "Available" - Mean block
time: 0.986466 ms
>From what I understand NOT available will call setBlocksForRetrace(true) and
changes the behavior.
I do not experience this behavior on Intel Sandybridge. The behavior is more
easily triggered when X has problems (plugging in my headset makes X input
handling freeze) or when KWin QML is loaded (long block?).
I'm interested fixing this but am not familiar enough with the swapping code.
Where to look at and how can I start KWin with going directly in the "broken"
code path?
--
You are receiving this mail because:
You are watching all bug changes.
