https://bugs.kde.org/show_bug.cgi?id=490358
--- Comment #13 from Zamundaaa <xaver.h...@gmail.com> --- It has half the dropped frames, so that's something at least. > and started typing in IntelliJ, which also reproduces the frame drops That probably does autocomplete predictions, which do take some CPU temporarily. If the scheduler is annoying, it might cause the issue... As in both cases the very vast majority of dropped frames are from missing the commit deadline, we probably need to increase the 1.5ms from https://invent.kde.org/plasma/kwin/-/blob/457b3a47ffe91b335ab18170cfb830d35217b9a8/src/backends/drm/drm_commit_thread.cpp#L296 for you. Could you compile KWin and see if that actually helps? I have an idea for how to automatically decide when that needs to be increased, but I don't really want to blindly make changes without knowing if it's really the problem. -- You are receiving this mail because: You are watching all bug changes.
