https://bugs.kde.org/show_bug.cgi?id=467574
--- Comment #12 from Prajna Sariputra <putr...@gmail.com> --- Just patching out the QCWarning line does not resolve the problem of KWin using 100% of a single core in my case, I have to either revert KWin to 5.27.4.1 or revert commit 226d8c0a3b464f8870c45bfe5079f042a3cd5d67 (screencast: Ensure we respect the negotiated framerate) on top of KWin 5.27.5 to get that issue to go away. Also, I have filed bug 469777 specifically for the issue of high KWin CPU usage and the extremely high amount of "kwin_screencast: Dropping a screencast frame because the compositor is slow" messages (well beyond the 20-30 per second noted in this bug report originally, like hundreds or even up to a thousand per second), since my specific issue happened on 5.27.5 while this bug report is for 5.27.3, so they seem like different issues to me. I also don't see any issues with the recording output, but then again I only ever record at 60fps at most. -- You are receiving this mail because: You are watching all bug changes.
