Bug 407046

Summary: Changing color scheme makes Xorg eat up memory and eventually stalls system
Product: [Plasma] kwin Reporter: Knut Hildebrandt <post>
Component: effects-variousAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: kde
Priority: NOR    
Version First Reported In: 5.15.4   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Xorg using 7 GB of memory
Memory usage of Xorg after changing color scheme twice - sorted by memory
Memory usage after changing color scheme twice - sorted by X11 memory

Description Knut Hildebrandt 2019-04-29 09:41:25 UTC
Created attachment 119710 [details]
Xorg using 7 GB of memory

Changing "color scheme" various times causes Xorg to allocate great amounts of memory - see attached screenshot. Usually Xorg uses about 60 MB. After changing the color scheme four or five times it had allocated more than 7 GB and used up almost all my memory and swap. 


SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2
Comment 1 David Edmundson 2019-04-29 09:44:06 UTC
We need to see where the memory is used.

ksysguard has a column for X resource usage per process
Comment 2 Knut Hildebrandt 2019-04-29 09:54:49 UTC
Do you mean the "X11 memory" column?
Comment 3 David Edmundson 2019-04-29 09:58:30 UTC
yes, that one
Comment 4 Knut Hildebrandt 2019-04-29 10:06:54 UTC
Created attachment 119711 [details]
Memory usage of Xorg after changing color scheme twice - sorted by memory
Comment 5 Knut Hildebrandt 2019-04-29 10:09:50 UTC
Created attachment 119712 [details]
Memory usage after changing color scheme twice - sorted by X11 memory
Comment 6 Bug Janitor Service 2019-05-14 04:33:08 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Christoph Feck 2019-05-14 19:20:24 UTC
New information was added with comment #4 and comment #5; changing status for inspection.
Comment 8 David Edmundson 2023-05-11 08:42:06 UTC
I could not reproduce this issue, can you confirm it's still an issue on Plasma 5.27
Comment 9 Bug Janitor Service 2023-05-26 03:45:38 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Bug Janitor Service 2023-06-10 03:45:34 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!