Bug 359426 - Plasmashell process uses a huge amount of memory making the computer overloaded and KDE unresponsive
Summary: Plasmashell process uses a huge amount of memory making the computer overload...
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: master
Platform: Debian testing Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-02-15 10:27 UTC by Gábor Nagy
Modified: 2018-10-27 04:14 UTC (History)
3 users (show)

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


Attachments
screenshot showing the problem (849.65 KB, image/jpeg)
2016-02-15 10:31 UTC, Gábor Nagy
Details
Plasmashell memory details shown in System Activity (266.88 KB, image/png)
2016-09-05 22:55 UTC, Raman Gupta
Details
Plasmashell System Activity (40.22 KB, image/png)
2016-09-05 22:56 UTC, Raman Gupta
Details
Plasmashell glances processes sorted by memory (135.31 KB, image/png)
2016-09-06 07:26 UTC, Raman Gupta
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gábor Nagy 2016-02-15 10:27:27 UTC
I have noticed that since the Debian stable -> testing upgrade my computer sometimes becomes extremely slow with high disk activity. From KDE I can't fix the problem, eventually everything just stops. I used to switch off the computer to be able to work again.

I could not find a reason why this happens or what triggers this behaviour.

Recently I have noticed that I can switch to the character console and work there. From the console I have noticed that the plasmashell process use a huge amount of memory.
Killing the plasmashell process restored the responsiveness in the graphical interface and the already running applications, so I could finish and save my work and properly close the applications.

Reproducible: Sometimes
Comment 1 Gábor Nagy 2016-02-15 10:31:10 UTC
Created attachment 97226 [details]
screenshot showing the problem
Comment 2 Raman Gupta 2016-09-01 14:25:38 UTC
I have the same issue on Fedora 23 Plasma 5.7.3 on QT 5.6.1. Plasmashell just uses up more and more memory (as well as CPU to some extent), and gets more and more sluggish over the course of a day or so. For example, clicking on a taskbar button takes a noticeably long time to bring up the clicked application.

Restarting it with `kquitapp5 plasmashell && sleep 5 && kstart plasmashell` restores snappy operation.
Comment 3 David Edmundson 2016-09-03 08:30:31 UTC
That screenshot says %mem 1.2 

1.2% is not a lot.

Do you use nvidia?
Comment 4 Raman Gupta 2016-09-03 13:34:22 UTC
I can't speak for OP but

a) My mem usage goes a lot higher than 1.2% (on a system with 32 gb). I'll let it collect memory for a while and then post a screenshot.

b) I use ATI with the open source radeonsi driver. Rendering backend is OpenGL 2.0.
Comment 5 Raman Gupta 2016-09-05 22:55:55 UTC
Created attachment 100944 [details]
Plasmashell memory details shown in System Activity

After about two days, Plasmashell is using about 2.6GB of memory privately.
Comment 6 Raman Gupta 2016-09-05 22:56:54 UTC
Created attachment 100945 [details]
Plasmashell System Activity

... and after about two days, Plasmashell is using about 8% of the CPU constantly, even when idle.
Comment 7 Raman Gupta 2016-09-06 07:26:07 UTC
Created attachment 100948 [details]
Plasmashell glances processes sorted by memory

Glances top processes sorted by memory. Plasmashell up to 90.3% CPU, 11.6% memory, 72GB virtual mem usage, 3.65G resident.
Comment 8 Raman Gupta 2016-09-26 23:20:58 UTC
Interesting: I haven't had this issue recently, even though Plasmashell and QT are both still the same version as before (5.7.3 and 5.6.1 respectively), and as far as I know I haven't changed any settings at all. Though I have updated a few other components, none of which seem remotely relevant, except *maybe* the following:

* kernel (now at 4.7.3)
* ibus (now at 1.5.11)
* chromium-libs-media (now at 52.0.2743.116-10)
Comment 9 Andrew Crouthamel 2018-09-26 22:17:15 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 set the bug status 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 Andrew Crouthamel 2018-10-27 04:14:24 UTC
Dear Bug Submitter,

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!