Bug 1396740 - KDE 5 plasmashell process uses 2.5G of RAM
Summary: KDE 5 plasmashell process uses 2.5G of RAM
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-workspace
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-19 14:52 UTC by Basic Six
Modified: 2017-08-08 19:18 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-08-08 19:18:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
KDE plasmashell process using 2.5G of RAM (104.87 KB, image/png)
2016-11-19 14:52 UTC, Basic Six
no flags Details

Description Basic Six 2016-11-19 14:52:55 UTC
Created attachment 1222160 [details]
KDE plasmashell process using 2.5G of RAM

Description of problem:

On a system that's just been sitting there for a few days, KDE is using a lot of resources. The plasmashell process is slowing everything down significantly by using a lot of CPU power and, most importantly, 2.5 GB (G!) of RAM. See attached screenshot.

When the attached screenshot was taken, the system had not been used for a day. Firefox is obviously running and using it's share of memory (which is not unusual for Firefox), as well as a handful of Chrome tabs and a file manager.



Version-Release number of selected component (if applicable):

Fedora 24
plasmashell 5.6.5



How reproducible:

Not sure if it's always this extreme. But KDE 5 generally seems to slow down over time.



Steps to Reproduce:
1. Use KDE 5, have a few browser windows open.
2. Let it run, don't reboot every day.
3. KDE slows down and sometimes uses a lot of RAM.



Actual results:

2.5G RAM usage by plasmashell on a system that should really be idling.



Expected results:

KDE processes should use less than 1 GB of RAM.



Additional info:

Maybe KDE 5 does some intense calculations in the background by default, which can be turned off? However, it is the plasmashell process which is using so much RAM.

Comment 1 Rex Dieter 2016-11-19 15:06:45 UTC
I see you mentioned plasma 5.6.5, there a much newer versions available in updates, please test those.  Unless 5.6.5 was a typo?  meaning 5.7.5 ?

Comment 2 Fedora End Of Life 2017-07-25 23:56:56 UTC
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.

Comment 3 Fedora End Of Life 2017-08-08 19:18:53 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.