Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 968655 [details] kprocess picture showing the amount of used memory by plasma-desktop process Description of problem: plasma-desktop eats up all of the memory on my system. I usually leave my computer turned on continuously, and today I went to use it and it was very, very slow. Running kprocess I saw that plasma-desktop was using approximately 14 GB of RAM, and this usage was increasing steadily, for no apparent reason. The problem also occurred yesterday, but only today I could take a look into my desktop before it had become unusable. Version-Release number of selected component (if applicable): kde-workspace-4.11.14-2.fc20.x86_64 How reproducible: always. Steps to Reproduce: 1. Log into KDE as a user. 2. Use KDE desktop normally. 3. After some time, tasks start to be killed with "Out of memory" messages. (See attached snippet of "messages.log") Actual results: Plasma-desktop eats up all of the available memory and it is killed by OOM killer. Expected results: Plasma-desktop should be well-behaved regarding use of RAM. Additional info: The only kde packages which have been updated in the last week (when the problem started appearing) are as follows: Dec 12 21:01:28 wotan yum[13444]: Updated: kde-baseapps-common-4.14.3-4.fc20.noarch Dec 12 21:01:45 wotan yum[13444]: Updated: kdepasswd-4.14.3-4.fc20.x86_64 Dec 12 21:01:46 wotan yum[13444]: Updated: 6:kde-plasma-folderview-4.14.3-4.fc20.x86_64 Dec 12 21:02:01 wotan yum[13444]: Updated: kde-baseapps-4.14.3-4.fc20.x86_64 Dec 12 21:02:14 wotan yum[13444]: Updated: kde-baseapps-libs-4.14.3-4.fc20.x86_64 Dec 13 19:01:31 wotan yum[20104]: Updated: kde-plasma-nm-0.9.3.5-2.fc20.x86_64 Dec 13 19:01:41 wotan yum[20104]: Updated: kde-plasma-nm-pptp-0.9.3.5-2.fc20.x86_64 Dec 13 19:01:42 wotan yum[20104]: Updated: kde-plasma-nm-vpnc-0.9.3.5-2.fc20.x86_64 Dec 13 19:01:42 wotan yum[20104]: Updated: kde-plasma-nm-openconnect-0.9.3.5-2.fc20.x86_64 Dec 13 19:01:42 wotan yum[20104]: Updated: kde-plasma-nm-openvpn-0.9.3.5-2.fc20.x86_64
Created attachment 968656 [details] snippet of /var/log/messages showing the OOM killer killing plasma-desktop
Just verified when bubblemon is activated within the notification area, the memory leak problem indeed does happen in /usr/bin/plasma-desktop. The package belongs to kdeplasma-addons-4.14.3-1.fc20.x86_64 and thus the bug must be reassigned to this package.
Reassigned
The same also happens on Fedora 21.
One simple way to reproduce the above on my system is by copying/moving large size files from/to external usb hdd.
I'm not sure if this would be helpful, but I found this on SDDM github's issue; https://github.com/sddm/sddm/pull/304
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.