https://bugs.kde.org/show_bug.cgi?id=469777
--- Comment #1 from Prajna Sariputra <putr...@gmail.com> --- > I guess that MR might just be exacerbating an existing issue though, I have > been getting `kwin_screencast: Dropping a screencast frame because the > compositor is slow` messages appear repeatedly in journalctl anytime a > screencast session is active, but with 5.27.5 as well as with 5.27.4.1 with > that MR applied I get way more of those (from like 20 per second to well over > 1000 per second). Correction: The warning messages I was getting prior to 5.27.5 is actually `Dropping a screencast cursor update because the compositor is slow`, so that part isn't as much "more warning messages than before" as it is "new warning messages". Looking through old logs I did still see the screencast frame drop message, but it was only occasionally occurring back then. Also, out of the 3 commits introduced in the problematic MR I found that the issue is specifically caused by commit 226d8c0a3b464f8870c45bfe5079f042a3cd5d67 (screencast: Ensure we respect the negotiated framerate), reverting it on top of 5.27.5 drops KWin's CPU usage back to what it was before. -- You are receiving this mail because: You are watching all bug changes.
