Bug 108269

Summary: high 100% cpu usage when one download complete and others running
Product: [Applications] kget Reporter: Gašper Ažman <gasper.azman>
Component: generalAssignee: KGet authors <kget>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:

Description Gašper Ažman 2005-06-28 15:09:59 UTC
Version:            (using KDE KDE 3.4.1)
Installed from:    Gentoo Packages
Compiler:          gcc-i686-pc-linux-gnu 3.4.4 
OS:                Linux

No plugins loaded (as far as I can tell :D, Konqueror integration enabled).

No crash, no backtrace.

Bug description:
When I have a long list of files (most of them above 1GB in size) to download, it runs normally for a time, and after the 1st download completes and one is still running, processor-usage jumps to 100% + 5% (HT processor) and stays there indefinitely while the downloads continue to run normally.

It might be important to note that this happens not only if the kget window is open but also if it is running in the taskbar only or is minimised, so it is not the refresh bug that has been noted here.

My guess would be an infinite loop.

Reproduce:
Start downloading some large files, with max_connections 2 (or more?).
When the 1st one of the two finishes, cpu usage becomes insanely high.

Expected behaviour:
Processor usage should stay at normal levels.

Notes:
When you close KGet and reopen it after the processor-usage-jump, the downloads resume normally and processor usage is back to normal.
Comment 1 Gašper Ažman 2005-06-28 15:12:12 UTC
Another file just completed and the processor-usage has not jumped. Maybe it IS the dreaded refresh bug... Weird. Will post more comments if I find anything.
Comment 2 Gašper Ažman 2005-06-28 19:17:53 UTC
Please mark duplicate of bug 58726.

http://bugs.kde.org/show_bug.cgi?id=58726
Comment 3 Nickolas Grigoriadis 2006-12-11 06:33:38 UTC
I find the same problem here:
Gentoo KGet 3.5.5.
NOT the refresh bug (does not drop CPU usage if minimized), but described exactly as above.
After first download finishes, CPU usage jumps to 100%, even after you stop all downloads.
Comment 4 miso kubo 2008-03-07 20:54:33 UTC
why is this marked as RESOLVED??

still happens. in 3.5.8
Comment 5 Urs Wolfer 2008-03-07 20:57:02 UTC
miso kubo: because it is a duplicate anyway, and has been fixed in KGet for KDE 4.0.