| Summary: | Stutter or bad frame timing in some situations with Plasma 6.6 beta | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Michael Marley <michael> |
| Component: | performance | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | akselmo, michael, xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | 6.5.91 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Michael Marley
2026-02-08 16:51:56 UTC
Can't repro on KDE Linux, though im on regular desktop PC Operating System: KDE Linux 2026-02-09 KDE Plasma Version: 6.6.80 KDE Frameworks Version: 6.24.0 Qt Version: 6.10.2 Kernel Version: 6.18.7-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 16 GiB of RAM (15.5 GiB usable) Graphics Processor: AMD Radeon RX 6600 My monitor is 3440x1440@165hz I did some more testing and found that I could not reproduce it on my 120Hz screen with the same laptop (whether or not Adaptive Sync was enabled made no difference). I also could not reproduce it on another laptop with Intel graphics, which makes me think that the AMD panel self refresh implementation likely has something to do with it. The problem definitely appeared with Plasma 6.5.91 (I never tested 6.5.90) and goes away if I revert to 6.5.5 though. If you put
> KWIN_DRM_OVERRIDE_SAFETY_MARGIN=1500
into /etc/environment, does that help?
Almost forgot to add that you need to reboot for it to apply That doesn't seem to have any effect. Something I neglected to mention earlier is that it isn't possible to reproduce the issue if I'm also running something like vkcube or even waving the mouse around at the same time. Okay, that's the only frame timing related thing that changed vs. 6.5. If you also set KWIN_USE_OVERLAYS=0, does that help? Hmm, that's really odd then. I tried disabling overlays already and that had no effect either. I thought they were disabled by default now anyway? Overlays are still disabled by default in releases, but not for development and beta versions. If you set https://invent.kde.org/plasma/kwin/-/wikis/Environment-Variables#kwin_log_performance_data, maybe that will at least show where it's dropping frames. Other than that, likely a bisect is the only way to find out what caused this. I tried setting KWIN_USE_OVERLAYS=0 again and this time it seems to have cleared up the issue. Perhaps I forgot to reboot the last time or maybe I'm just going crazy. I'm guessing the performance log data is no longer useful. Anyway, it seems this isn't actually a (kwin) bug. Sorry to waste your time. It's very interesting it causes problems on the 60Hz display but not on the 120Hz one though... Anyways, this was not a waste of time, because I was tempted to enable overlays by default for AMD APUs, and now I'll definitely wait longer until we risk that. I did some more experimenting and I think what I said in Comment 2 is correct; it is some kind of interaction between PSR and layers. If I have both of those on, I get the issue. If I have either one of them off, I do not get the issue. That of course also explains why I could not reproduce it on the 120Hz screen since that doesn't have PSR. I've done yet more testing and I'm now pretty sure what I said about the CSS spinners page being jerky is a red herring; it is either caused by the page itself or by Firefox. Other smoothness tests like https://testufo.com/ do not drop frames and the frame drops on the CSS spinners page come and go both with layers on and off. In general, the juddery cursor in Konsole was the only issue I was able to find with layers, and that's a nitpick even by my standards. I couldn't reproduce any of the framedrops that were happening with layers from 6.5.x. And probably no-one else is going to care about the Konsole kursor. Aaaaand, I just reproduced the cursor jumping with layers turned off. This is a PSR issue and not a kwin issue at all. Please ignore this entire report and accept my apologies. |