Bug 258911

Summary: Kget launches a number of kio_http processes using up to 60% CPU
Product: [Applications] kget Reporter: Alexander Borghgraef <iskendar>
Component: CoreAssignee: KGet authors <kget>
Status: RESOLVED FIXED    
Severity: normal CC: mat69
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Alexander Borghgraef 2010-12-05 15:04:39 UTC
Version:           unspecified (using KDE 4.5.1) 
OS:                Linux

I'm currently using firefox+flashgot with kget as download manager for all sorts of downloading purposes. Flashgot allows you to select a part of a webpage, from which it extracts all links, which you can then choose do download using the download manager of your choice, in my case kget. Problem is, when I do so, this launches a bunch of kio_http processes which start then hogging the CPU (when I reported this to the forum, three were running using up 60% of it). Killing them all doesn't interrupt any of the downloads, so I wonder what they're actually for, though new ones keep popping up. 

I'm using kget 2.5.1, KDE 4.5.1, firefox 3.6.12, flashgot 1.2.6 on kubuntu 10.10

Reproducible: Always

Steps to Reproduce:
Select website links with flashgot, this adds them to the download queue in kget. Kget gets any authentication data (for e.g. rapidshare) from cookies stored by konqueror. 

Actual Results:  
Kget downloads up to 2 files at a time (default settings). This causes a number of kio_http processes to start up. For a single avi file, their CPU use summed to 15% (the top single process up to 9%). When dealing with a long queue, I've witnessed up to 60% use divided over three processes.

Expected Results:  
It was suggested that the kio_slaves were determinging the mime types of the files in the queue. Obviously, this should be a low priority process using up little CPU time.
Comment 1 Matthias Fuchs 2011-09-29 15:17:16 UTC
This should be fixed by now. Please reopen this report if the problem still exists in 4.7 or newer.