Bug 373627

Summary:	Hight CPU when screen goes off for energy saving.
Product:	[Plasma] kwin	Reporter:	hotmusicfan
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	bshah, kde, plasma-bugs-null
Priority:	NOR	Keywords:	investigated, triaged
Version First Reported In:	5.12.5
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description hotmusicfan 2016-12-13 23:12:06 UTC

Hello!

When screen is dimming as configured in "Power management" I'm experiencing high CPU. I notice it because I often leave my music playing while doing something else and exactly when screen is dimming the sound gets ragged or even stops for a while and when I return to work on the computer it takes a while to present the desktop after tapping on the touchpad or press some key.

Comment 1 hotmusicfan 2017-01-16 15:01:59 UTC

Hi again! 
My mistake - it is not when screen is dimming but when screen switches off for energy saving.
Issue is on openSUSE Leap 42.2 with Plasma 5.8.3 and nVidia proprietary driver.

Comment 2 hotmusicfan 2017-01-26 23:16:36 UTC

In these cases the processes which have the highest CPU usage are X and kwin_x11.

Comment 3 hotmusicfan 2017-10-20 20:23:56 UTC

Same on Leap 42.3/Plasma 5.8 LTS.

Comment 4 hotmusicfan 2018-08-05 01:03:05 UTC

Problem still available on openSUSE Leap 15/Plasma 5.12 LTS.
From various opinions in the web it seems that this is most likely a problem with KWin. So at least just answer will you backport KWin performance enhancement from Plasma 5.13 to 5.12? If the answer is "Yes" you can close this one.

Comment 5 David Edmundson 2018-08-05 12:44:56 UTC

High CPU in what process?

Comment 6 hotmusicfan 2018-08-05 14:01:51 UTC

(In reply to David Edmundson from comment #5)
> High CPU in what process?

See comment 2.

Comment 7 Andrew Crouthamel 2018-09-19 14:34:49 UTC

This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.

Comment 8 hotmusicfan 2018-09-20 00:30:53 UTC

(In reply to Andrew Crouthamel from comment #7)
> This bug has had its resolution changed, but accidentally has been left in
> NEEDSINFO status. I am thus closing this bug and setting the status as
> RESOLVED to reflect the resolution change.

It is not resolved at all because it is still existing and as far as I know there is not any patch for it. If there is another report for this bug where the things are different please let me know.
Greetings!