https://bugs.kde.org/show_bug.cgi?id=476712

            Bug ID: 476712
           Summary: Compositing sometimes locks to 30 FPS instead of 60,
                    with no clear pattern
    Classification: Plasma
           Product: kwin
           Version: 5.27.9
          Platform: Archlinux
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: compositing
          Assignee: kwin-bugs-n...@kde.org
          Reporter: omg-ichfind-keinen-na...@protonmail.com
  Target Milestone: ---

SUMMARY
***
(I am not entirely sure what exactly if kwin is causing it but, ) 
As long as my compositor is running, I get strange behavior.
My frame-rate sometimes seems to get locked at 30/31FPS, with no clear
indication why.
It does not happen by itself, sometimes maximizing or minimizing a windows
fixes it, until the next window change.
But not always, so the cause seems very hard to figure out. While my cursor
doesn't seem to be affected by it, all my applications are, Browser,
Media-Player, (non-full-screen) Games etc. 
Moreover my Applications cannot notice the difference, they claim to run at
60FPS but using the "Show FPS" effect from the settings, I was able to make
sure my frame-rate is actually jumping between 30 and 60FPS.
My browser (Brave flatpak) seems to affect it even more, right now, while
typing I see my frame-rate jumping between 30 and 60. I have tried many
different settings, disabling effects, trying all smoothness/responsiveness
settings for the compositor.
***


STEPS TO REPRODUCE
1. Login
2. Doing any kind of window Transformation
3. Notice FPS change

OBSERVED RESULT
Seemingly random 30FPS lock

EXPECTED RESULT
Smooth 60FPS with Vsync. (Like it used to be)


SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Arch linux, 
Kernel: 6.5.9-arch2-1 (64-bit)
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11
Using X11


ADDITIONAL INFORMATION
GPU is : GTX 1650 SUPER 
CPU: AMD RYZEN 5 3600
I am having this issue with 2 monitors right now, 
however I started using the second one not long after the the problem first
occurd.
Having this issue since my last system update, so nvidia driver might be
related/cause.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to