Bug 425450 - Memory consumption climbs higher on adding plasmoids and altering settings
Summary: Memory consumption climbs higher on adding plasmoids and altering settings
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-performance (show other bugs)
Version: 5.18.5
Platform: Ubuntu Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-17 09:36 UTC by Puspam Adak
Modified: 2025-02-14 03:46 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Memory consumption (95.39 KB, image/png)
2020-08-17 09:36 UTC, Puspam Adak
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Puspam Adak 2020-08-17 09:36:52 UTC
Created attachment 130928 [details]
Memory consumption

SUMMARY:

My KDE Plasma desktop is brand new. Currently, I have only one bottom panel, with a system tray, digital clock, task manager and a menu plasmoid on the panel (whatever comes by default). No dynamic wallpaper.

After logging in to Plasma, the memory consumption of the "plasmashell" process hovers at around 100MB. After about 10 mins of web browsing and other stuff, the memory consumption goes to around 200MB. Not only that, on changing settings and adding/removing widgets (i.e., configuring the desktop), the memory consumption increases rapidly. It stops increasing once I stop doing those.

According to me, this might be a memory leak issue, because the memory consumption only increases and never decreases unless I restart Plasma.

STEPS TO REPRODUCE
1. Note the memory consumption of the "plasmashell" process just after logging in.
2. Do anything or change some settings and then note the memory usage.

SOFTWARE/OS VERSIONS
Linux: Ubuntu 20.04
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Comment 1 Nate Graham 2023-09-19 20:21:31 UTC
Hello and thank you again for the bug report! Unfortunately we were not able to address it yet, nor even manage to reproduce the issue ourselves. Can we ask you to please check if this issue is still happening with Plasma 5.27?

If it is, please change the status to REPORTED. Thanks a lot!
Comment 2 Bug Janitor Service 2023-10-04 03:46:43 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 3 Bug Janitor Service 2023-10-19 03:46:05 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!
Comment 4 Puspam Adak 2023-11-16 09:59:02 UTC
(In reply to Nate Graham from comment #1)
> Hello and thank you again for the bug report! Unfortunately we were not able
> to address it yet, nor even manage to reproduce the issue ourselves. Can we
> ask you to please check if this issue is still happening with Plasma 5.27?
> 
> If it is, please change the status to REPORTED. Thanks a lot!

Yes, the issue is still present in Plasma 5.27.
Comment 5 Nate Graham 2025-01-15 18:57:31 UTC
Is this still happening in a recent version of Plasma, like 6.2.5 or later?
Comment 6 Bug Janitor Service 2025-01-30 03:47:16 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2025-02-14 03:46:44 UTC
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.