Bug 148463

Summary:	Kget is eating 60% to 90% of CPU on a 1.8GHz Centrino Duo with 1 active download
Product:	[Applications] kget	Reporter:	Uqbar <regmeplease>
Component:	general	Assignee:	KGet authors <kget>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version:	0.8.5
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description Uqbar 2007-08-02 21:11:50 UTC

Version:           0.8.5 (using KDE KDE 3.5.6)
Installed from:    Ubuntu Packages
OS:                Linux

I do know about https://bugs.kde.org/show_bug.cgi?id=51965 .
But after some years, the problem is still here.
It doesn't matter how long the download list is, and even whether the application is minimised in
the taskbar or maximised on the display. When mimimised the application eats less than 70%.
When maximised it's eating from a minimum of 60% up to 90% of the CPU time of one of the two cores.
So part of the problem can be in the GUI.

Comment 1 Urs Wolfer 2007-08-02 23:42:31 UTC

If you know about #51965, then you have probably also seen my last comment there ;)

Comment 2 Uqbar 2007-08-02 23:50:22 UTC

On Thursday 02 August 2007 23:42:32 Urs Wolfer wrote:
[bugs.kde.org quoted mail]

Well I read that link and thought that the problem was not
related to KDE.

So the high CPU load is an unfixable bug while under KDE 3.x. Isn't 
it?

As it seems KDE is approaching the v4 release, I think I'll go
the "curl" way in the meantime.

Comment 3 Urs Wolfer 2007-08-02 23:55:09 UTC

We just don't have the manpower to work on the KDE 3 version.

You could try to delete the KGet config files. I don't know if that helps...
~/.kde/share/config/kgetrc

Comment 4 Uqbar 2007-08-03 00:04:44 UTC

On Thursday 02 August 2007 23:55:10 Urs Wolfer wrote:
[bugs.kde.org quoted mail]

It seems it works! Now workload is below 1%.
This is really weird though!

I'd put this adivse somewhere in the bug system.

Thanks a lot.

Comment 5 Uqbar 2007-11-12 09:15:25 UTC

I'have no idea whether in KDE 4 this problem has been fixed or investigated.
In any case it seems to me that the problem arises when there are recovered downloads. Otherwise the CPU load remains below 1% even for days.