Bug 1175578

Summary:

after update to kde-plasma-nm 0.9.3.5-2, kde-plasma grows in memory and cpu, especially with rekonq and choqok

Product:

[Fedora] Fedora

Reporter:

Luke <luton>

Component:

kde-workspace

Assignee:

Than Ngo <than>

Status:

CLOSED EOL

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

urgent

Docs Contact:

Priority:

unspecified

Version:

CC:

dvratil, jgrulich, jreznik, kevin, ltinkl, mbriza, meta, rdieter, rnovacek, than

Target Milestone:

---

Target Release:

---

Hardware:

x86_64

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2015-06-29 23:51:03 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
KDE packages versions	none
strace of plasma-desktop when taking around 30% of RAM after a computer has been left idle for a few hours	none
timing of plasma-desktop after a computer left idle for a few hours	none
strace of plasma-desktop when running choqok	none
strace of choqok	none
ps of plasma-desktop with choqok	none
yum update log leading to a problem	none
valgrind --tool=memcheck --leak-check=full --log-file=valgrind_plasma.log plasma-desktopresult of	none
plasma-desktop stdout and stderr (run with valgrind in above comment)	none

Description Luke 2014-12-18 05:18:22 UTC

Description of problem:

After a recent update of kde-plasma-nm, the KDE desktop under Fedora became basically useless.

The problem is that with time plasma-desktop consumes more and more memory, eventually leading to swapping and a need for a forced reboot.

This happens even when a computer is left idle, after a few hours.

Below I attach a strace of plasma-desktop after a computer was left idle for a few hours:
plasma-desktop-strace-idle

together with the timing strace
plasma-desktop-strace-idle-timing

A detailed yum update result leading to this problem, before it did not occur at all:
yum-update-log

When I restart a computer, plasma-desktop would stay at around 25% of RAM. I noticed the two applications which really speed up the consumption of RAM and memory: rekonq and choqok. Choqok actually takes a lot of time to boot, and after dozens of minutes it ends up consuming around 35% of memory.

Below I attach a strace of plasma-desktop when turning choqok on, together with a strace of choqok itself:
plasma-desktop-with-choqok-strace
choqok-strace
choqok-strace-timing

This started to happen after an update of kde-plasma-nm, no update of affected plasma-desktop nor chqok nor rekonq.

Version-Release number of selected component (if applicable):
kde-plasma-nm.x86_64 0.9.3.5-2.fc20

How reproducible:
Always

Steps to Reproduce:
1. yum update to kde-plasma-nm.x86_64 0.9.3.5-2.fc20
2. see plasma-desktop taking lots of RAM, especially with choqok and rekonq

Actual results:
Takes more and more RAM, leading to swapping and, finally, a forced reboot is necessary. That unfortunately makes a Fedora/KDE unusable.

Expected results:
should stay at relatively low RAM usage, as before the update

Additional info:
Fedora 20 on Macbook Pro
Linux mcb 3.16.4-200.fc20.x86_64 #1 SMP Mon Oct 6 12:57:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
with nouveau

Comment 1 Luke 2014-12-18 05:19:27 UTC

Created attachment 970384 [details]
KDE packages versions

List of KDE packages versions.

Comment 2 Luke 2014-12-18 05:20:33 UTC

Created attachment 970385 [details]
strace of plasma-desktop when taking around 30% of RAM after a computer has been left idle for a few hours

Comment 3 Luke 2014-12-18 05:21:14 UTC

Created attachment 970386 [details]
timing of plasma-desktop after a computer left idle for a few hours

Comment 4 Luke 2014-12-18 05:21:47 UTC

Created attachment 970387 [details]
strace of plasma-desktop when running choqok

Comment 5 Luke 2014-12-18 05:22:26 UTC

Created attachment 970388 [details]
strace of choqok

Comment 6 Luke 2014-12-18 05:23:34 UTC

Created attachment 970389 [details]
ps of plasma-desktop with choqok

Comment 7 Luke 2014-12-18 05:24:13 UTC

Created attachment 970390 [details]
yum update log leading to a problem

Comment 8 Jan Grulich 2014-12-18 09:25:10 UTC

Hmm, I don't think that the problem is in kde-plasma-nm. In the update you mentioned I added just a simple missing option for OpenVPN connections, which definitely doesn't have any effect on plasma-desktop.

Comment 9 Luke 2014-12-18 10:04:40 UTC

OK, I assumed it was so due to that package being the only one connected to plasma-desktop. I switched the component to kde-workspace since there is no plasma-desktop component of its own.

Comment 10 Luke 2014-12-19 14:51:28 UTC

Created attachment 971200 [details]
valgrind --tool=memcheck --leak-check=full --log-file=valgrind_plasma.log plasma-desktopresult of

Result of running valgrind after killing plasma-desktop.

Comment 11 Luke 2014-12-19 14:54:00 UTC

Created attachment 971201 [details]
plasma-desktop stdout and stderr (run with valgrind in above comment)

Comment 12 Luke 2015-02-27 02:56:34 UTC

Similar problems reported in KDE Bugzilla:

https://bugs.kde.org/show_bug.cgi?id=342374

Comment 13 mathew 2015-02-28 20:32:51 UTC

Same problem here with Fedora 20. I've been forced to give up and switch to XFCE until there's a fix.

Comment 14 Rex Dieter 2015-03-01 15:44:02 UTC

I'm betting this bug has more to do with legacy systray icons (as mentioned in Summary wrt rekonq and choqok) and less to do with plasma-nm

Comment 15 Fedora End Of Life 2015-05-29 13:31:23 UTC

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.

Comment 16 Fedora End Of Life 2015-06-29 23:51:03 UTC

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.