Bug 179037 - some (sometimes unidentified) process is occupying 50 % to 100 % CPU and is not killable
Summary: some (sometimes unidentified) process is occupying 50 % to 100 % CPU and is n...
Status: RESOLVED NOT A BUG
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: 4.1.0
Platform: Mandriva RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-29 11:52 UTC by jan sekal
Modified: 2009-06-05 15:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
some unknown process is eating CPU and there is no way how to determin what is it and how to kill it (60.53 KB, image/png)
2008-12-29 11:56 UTC, jan sekal
Details
background CPU consumption (81.14 KB, image/png)
2008-12-29 14:21 UTC, jan sekal
Details
huge cpu need (110.94 KB, image/png)
2008-12-29 14:24 UTC, jan sekal
Details
some unidentified process eats 100 % cpu (125.67 KB, image/png)
2009-01-02 20:44 UTC, jan sekal
Details
the same as attachment 29839 (122.29 KB, image/png)
2009-01-02 20:45 UTC, jan sekal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jan sekal 2008-12-29 11:52:46 UTC
Version:            (using KDE 4.1.0)
OS:                Linux
Installed from:    Mandriva RPMs

how to reproduce this bug:

install Kubuntu 8.10/Mandriva 2009.0/Fedora 10 KDE (all featuring kde 4.1)
switch on the program "System Monitor"
run firefox (versions shipped with that installations), click some web pages
run Krusader 2.00

after some time (approx 10 min) CPU load jumps to 100 %, and in the System Monitor you even do not know why (screenshots included)

once it happened to me, that this process eating 100 % CPU was krusader, but i could not kill it, even as root, and the process was designated as owned by root. after re-login, the process was still running
Comment 1 jan sekal 2008-12-29 11:56:56 UTC
Created attachment 29720 [details]
some unknown process is eating CPU and there is no way how to determin what is it and how to kill it

some unknown process is eating CPU and there is no way how to determin what is it and how to kill it
Comment 2 jan sekal 2008-12-29 14:21:12 UTC
Created attachment 29725 [details]
background CPU consumption

this screenshot shows, how much of my 1,5 GHz processor is occupied (this is only the background!).
with previous version of kde, 3.5.1. the background was almost ten times lower (like 5 %) - if this huge jump in cpu need is inherent to kde 4+ then sorry about considering it a bug
Comment 3 jan sekal 2008-12-29 14:24:20 UTC
Created attachment 29726 [details]
huge cpu need

this screenshot shows, how much of my 1,5 GHz processor is occupied (this is only the background!).
with previous version of kde, 3.5.1. the background was almost ten times lower (like 5 %) - if this huge jump in cpu need is inherent to kde 4+ then sorry about considering it a bug
this change is very easily noticed by laptop user, because the cooling fan has several gears
furthermore, I noticed the enormous jump in cpu need because the desktop is remarkably slow (as compared to kde 3.5.9)
Comment 4 jan sekal 2009-01-01 20:28:04 UTC
further testing with KDE 4.1 Mandriva 2009.1 revealed, that the huge cpu need is probable due to the .... of the "system monitor".
if the system monitor is off, the fan of my cpu is off as well, which indicates, that the cpu usage is no more than ~ 6%
the system monitor has always been a bad guy .. e.g. in Suse ~10.2+ it prevented the resume from suspend to ram, so one had to switch it off before every suspend, which made this linux out of usability
Comment 5 jan sekal 2009-01-02 20:44:31 UTC
Created attachment 29839 [details]
some unidentified process eats 100 % cpu

another example - in the system monitor, you do not know what is eating the cpu, so usually restart is needed.
Comment 6 jan sekal 2009-01-02 20:45:24 UTC
Created attachment 29840 [details]
the same as attachment 29839 [details]
Comment 7 Dario Andres 2009-01-07 22:05:32 UTC
Can you still reproduce this bug with a recent KDE (4.1.3 / 4.2beta2 / 4.2svn) ? 
You can install the program "top" and run it inside a Konsole window to get a proper CPU usage , and process list.
Thanks :)