https://bugs.kde.org/show_bug.cgi?id=489952
--- Comment #28 from pallaswept <[email protected]> --- (In reply to thesword from comment #27) > Maybe setting `KWIN_DRM_OVERRIDE_SAFETY_MARGIN` environment variable to a > lower value might help especially on a high refresh rate monitor. It's set > to 1500 by default. I'm seeing an increasing number of people noticing this bug lately (lots of mentions on reddit/forums/discord/etc), resulting in a lot of random guesses from random people, some of them with damaging consequences. I saw a guy's root partition need rebuilding after trying the NO_AMS variable on an nvidia card crashed his machine. Playing with a setting called 'override safety margin' is obviously inherently unsafe, so I would like to know more about this before I change it, since I'm definitely gonna be all alone trying to fix it if something goes wrong and I can't get online. What is this safety margin? What is the effect of decreasing it? The source says: // the 1.5ms on top of that was chosen experimentally, for the time it takes to commit + scheduling inaccuracies Which implies that, in order to commit earlier and not run late, this number should *larger*, but you said to set it smaller? Also, the documentation for this variable says: The issue usually manifests in only getting half the refresh rate of what you set the screen to. But that doesn't quite match our symptoms so doesn't fill me with confidence that I'm even trying the right thing. You're the kwin dev not me, so obviously I'm missing something here, but I'd just like to know what I'm doing before I do it, would you mind filling in some of the blanks for me? -- You are receiving this mail because: You are watching all bug changes.
