Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#45193 - [kdebase-workspace] Eating resources after last update

Attached to Project: Arch Linux
Opened by André Fettouhi (A.Fettouhi) - Wednesday, 03 June 2015, 18:30 GMT
Last edited by Antonio Rojas (arojas) - Thursday, 04 June 2015, 19:07 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Antonio Rojas (arojas)
Felix Yan (felixonmars)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I am still running KDE4 on my Arch Linux 64 bit machine and today there was a big update of some of the KDE apps to 15.04.2. Now my plasma-desktop runs from 0 % to 100 % on one core and is eating up my memory. Within 15 % I have gone from 1.8 GB RAM used to over 3 GB RAM used running nothing but the plasma-desktop.

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
1. Update Arch Linux with KDE4
2. Reboot
3. Login
This task depends upon

Closed by  Antonio Rojas (arojas)
Thursday, 04 June 2015, 19:07 GMT
Reason for closing:  Not a bug
Comment by Antonio Rojas (arojas) - Thursday, 04 June 2015, 08:14 GMT
Is this reproducible with a clean user?
Comment by André Fettouhi (A.Fettouhi) - Thursday, 04 June 2015, 10:04 GMT
I will have to check that out. I am work at the moment, so I can look at in roughly 7 to 8 hours.
Comment by André Fettouhi (A.Fettouhi) - Thursday, 04 June 2015, 19:02 GMT
Created a new user and KDE4 runs fine there. But I figured out what is causing the CPU spike on one core. It is the hardwareinfo widget for some reason. I have it running on my old user together with CPU etc. in the systeminfo widget that combines all stat widgets into one. But the stand-alone hardwareinfo widget also causes the spike. So please close this. Since this widget bug of some kind.

Loading...