https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #33 from pallaswept <[email protected]> --- (In reply to Zamundaaa from comment #32) > Nothing needed rebuilding... The machine froze and the forced shutdown caused disk corruption :( We got it back no problem :) Totally pilot error, not a KDE problem, but I was just trying to demonstrate that tinkering with settings might not be a good idea if we don't understand what they're doing. so: > > What is this safety margin? What is the effect of decreasing it? > It changes how long before a given refresh cycle KWin needs to commit the > next frame. And you should indeed increase it, reducing it won't help. Try > values up to like 5000µs, more than that may cause additional stutter rather > than prevent it. Thanks for clarifying! :) No luck with that one I'm afraid, it was worth a shot! > It seems that everyone affected is on NVidia. Do I assume correctly that all > of you are using the proprietary driver (rather than the open kernel modules > or Nouveau)? I tried the closed module, and also tried it with the firmware disabled, but it didn't have any bearing on this. I'm on the open module aside from that testing but I can switch if you want some testing done. I expect to get a little free time over the weekend and I'm very curious to see how those timing plots look with this new vblank parameter because it's visibly very different. Maybe it'll give us a hint. -- You are receiving this mail because: You are watching all bug changes.
