Hide Forgot
Description of problem: After multi hours usage on a laptop with external monitor attached, powered by Skylake CPU and GPU (i7-6700HQ), Plasma becomes slower and slower, even the mouse pointer slows down. I observed the plasmashell process using more and more CPU and RAM over time. Restarting plasmashell fixes the issue temporarly, it reappears after enough time. I just found another user on IRC (Lipsum) having the exact same problem. He also has multi monitor and Skylake. I filled this bug agains xorg-x11-drv-modesetting because when using Intel DDX (I recompiled the original Fedora RPM removing the patch disabling it for Skylake) problem seems not to be present. I have no idea if this is actually an issue Plasma itself (doesn't look like though), modesetting DDX, glamor or mesa. Please advise on this matter. Version-Release number of selected component (if applicable): root@enrico-dell ~ # rpm -qa | grep 'plasma-workspace-5\|mesa-dri\|modset\|xorg-x11-server-Xorg' xorg-x11-server-Xorg-1.18.4-4.fc24.x86_64 plasma-workspace-5.7.5-2.fc24.x86_64 mesa-dri-drivers-12.0.3-2.fc24.x86_64 How reproducible: always (after enough usage in time) Steps to Reproduce: 1. Multi monitor setup is required 2. Start a plasma session and use it normally 3. Monitor plasmashell CPU and RAM usage over time 4. Notice the performance of plasma, especially on the external monitor, become sluggish Actual results: Plasma uses more and more RAM and CPU, performance is degraded and user experience is affected (sluggish interaction, slow response from the plasma shell) Expected results: CPU and RAM usage should be faily constant over time. Responsiveness of the shell should be constant in time and not sluggish. Additional info: I'm not sure if a better than full HD monitor is required. I have the following configration: taglenri@enrico-dell ~ $ xrandr Screen 0: minimum 8 x 8, current 4480 x 1440, maximum 32767 x 32767 eDP1 connected primary 1920x1080+2560+0 (normal left inverted right x axis y axis) 350mm x 190mm 1920x1080 59.93*+ 1400x1050 59.98 1600x900 60.00 1280x1024 60.02 1280x960 60.00 1368x768 60.00 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.32 56.25 864x486 60.00 640x480 59.94 720x405 60.00 640x360 60.00 DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) HDMI1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 600mm x 340mm 2560x1440 59.95*+ 2048x1152 60.00 1920x1200 59.95 1920x1080 60.00 60.00 50.00 59.94 30.00 25.00 24.00 29.97 23.98 1920x1080i 60.00 50.00 59.94 1600x1200 60.00 1680x1050 59.88 1280x1024 75.02 60.02 1200x960 59.99 1152x864 75.00 1280x720 60.00 50.00 59.94 1024x768 75.03 60.00 800x600 75.00 60.32 720x576 50.00 720x576i 50.00 720x480 60.00 59.94 720x480i 60.00 59.94 640x480 75.00 60.00 59.94 720x400 70.08 HDMI2 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) As mentioned using the Intel DDX driver seems to improve the situation. I will keep keep testing with Intel DDX and report back if I can reproduce. If I may: would it be a good idea to enable again support for Skylake in Intel DDX? I know it was problematic for some people so modesetting can be kept as default. However, and this is true also for the very first moments after login, Intel DDX feels like a smoother experience for Plasma. Thank you.
So this is definitely a bug in Plasma, sorry for the initial confusion. It happens also with Intel DDX, but it's not as bad, probably because SNA is faster than glamor. It is quite easy to notice if enabling the "Slide back" effect for Kwin compositing. I guess the bug should be assigned to someone else, Dave is probably not the right person. I cannot do it though.
bugs.kde.org is the best place to get direct feedback from plasma devs
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.