Bug 58726

Summary: very high cpu usage when downloading to desktop with KGet while browsing webpages
Product: [Applications] kget Reporter: Rasmus Larsen <webmaster>
Component: generalAssignee: KGet authors <kget>
Status: RESOLVED DUPLICATE    
Severity: normal CC: amthpublic, gekylafas, ronstk
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Mandrake RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Rasmus Larsen 2003-05-20 20:44:34 UTC
Version:            (using KDE KDE 3.1)
Installed from:    Mandrake RPMs
OS:          Linux

When downloading a file to the desktop, in this case a 600 mb iso, I'm not able to use the web as it results in what seems to be a high cpu usage, eg. mouse lags and gets stuck for a while, and gui's generally seems to lag.
   If I then stop the download and browse (the same pages) again, it works fine. I've also tried downloading to another localtion and I don't seem to have any troubles.

It doesn't crash the system directly, but you have to be quite patient in order to restore the system, eg. opening the process manager, finding the process (konqueror) and killing it, while the mouse lags.

Mozilla seems to work fine while saving to the desktop.
Comment 1 Thiago Macieira 2003-05-20 20:54:53 UTC
*** Bug 58725 has been marked as a duplicate of this bug. ***
Comment 2 John Allen 2004-03-09 09:52:18 UTC
The high CPU usage is caused by th refresh rate of the KGet window. It seems to be refreshing continously. If you close the KGet window, the CPU usage drops to an acceptable 5-10%.
Comment 3 David Sibai 2004-04-01 23:52:55 UTC
I also experiment very high (100%) cpu usage with kget, however, it does not matter where I'm downloading to. It happens almost every time, I'm on a Debian/unstable stock KDE 3.2.1 system. 
I tried to close the kget window, it does not change anything, I have to exit kget to see the cpu usage dropping.
Comment 4 David Sibai 2004-06-20 13:54:02 UTC
The problem seems fixed in 3.2.3. Could anyone confirm this?
Comment 5 Georgios E. Kylafas 2004-07-14 12:30:12 UTC
On the contrary, I noticed the same behaviot (high CPU/Memory usage) in KDE 3.2.3, as well.

Comment 6 Axel V 2004-08-28 11:48:59 UTC
I experienced this problem too when I recently installed yoper-linux 2.1, but only when using the ext3 filesystem. I reinstalled with the reiserfs, and now I don't have this problem. Could that have anything to do with it?
Comment 7 Krzysztof Lichota 2004-10-03 18:42:44 UTC
Still present in KDE 3.3.0.
Comment 8 Sean E. Russell 2004-12-21 14:15:39 UTC
Still present in KDE 3.3.1
Comment 9 Γιώργος Κυλάφας (Giorgos Kylafas) 2005-02-09 09:20:58 UTC
It seems corrected in KDE 3.3.2
Comment 10 Gašper Ažman 2005-06-28 19:17:09 UTC
*** This bug has been confirmed by popular vote. ***
Comment 11 Gašper Ažman 2005-06-28 19:19:43 UTC
Still present in 3.4.1
Comment 12 Gašper Ažman 2005-06-28 19:26:06 UTC
The bugfix provided in this bugreport does not work for KDE 3.4.1: If I close the window, the cpu usage does NOT drop. Increased CPU usage starts when a download completes while another download is running, if window is open (even if it isn't shown). This happens regardless of where you are saving your stuff, and not just the desktop.
Comment 13 Ron Onstenk 2005-07-09 01:52:54 UTC
I have this problem too.
after typing: strace -p 3815 (pid of kget)
1000 repeatings of the folowing lines.
in ksysguard user% = 92


gettimeofday({1120865466, 472130}, NULL) = 0
gettimeofday({1120865466, 472889}, NULL) = 0
ioctl(4, FIONREAD, [0])                 = 0
gettimeofday({1120865466, 476011}, NULL) = 0
select(16, [3 4 5 6 8 15], [], [], {0, 0}) = 0 (Timeout)
gettimeofday({1120865466, 477988}, NULL) = 0
gettimeofday({1120865466, 478742}, NULL) = 0
ioctl(4, FIONREAD, [0])                 = 0
gettimeofday({1120865466, 480134}, NULL) = 0
select(16, [3 4 5 6 8 15], [], [], {0, 0}) = 0 (Timeout)
gettimeofday({1120865466, 481487}, NULL) = 0
gettimeofday({1120865466, 482213}, NULL) = 0
ioctl(4, FIONREAD, [0])                 = 0
gettimeofday({1120865466, 485663}, NULL) = 0
select(16, [3 4 5 6 8 15], [], [], {0, 0}) = 0 (Timeout)
gettimeofday({1120865466, 487115}, NULL) = 0
gettimeofday({1120865466, 487880}, NULL) = 0
ioctl(4, FIONREAD, [0])                 = 0
gettimeofday({1120865466, 490979}, NULL) = 0
select(16, [3 4 5 6 8 15], [], [], {0, 0}) = 0 (Timeout)


also found 1 interuption as


gettimeofday({1120865466, 137302}, NULL) = 0
select(16, [3 4 5 6 8 15], [], [], {0, 0}) = 1 (in [4], left {0, 0})
gettimeofday({1120865466, 146730}, NULL) = 0
gettimeofday({1120865466, 147498}, NULL) = 0
ioctl(4, FIONREAD, [32])                = 0
read(4, "\34\3664\332\7\0\0\4%\1\0\0\217F \t\0\0\0\0\217F \t\270"..., 32) = 32
ioctl(4, FIONREAD, [0])                 = 0
ioctl(4, FIONREAD, [0])                 = 0
gettimeofday({1120865466, 151051}, NULL) = 0
select(16, [3 4 5 6 8 15], [], [], {0, 0}) = 0 (Timeout)
gettimeofday({1120865466, 152501}, NULL) = 0
gettimeofday({1120865466, 153233}, NULL) = 0
ioctl(4, FIONREAD, [0])                 = 0
gettimeofday({1120865466, 154534}, NULL) = 0
Comment 14 Urs Wolfer 2005-09-20 14:18:42 UTC

*** This bug has been marked as a duplicate of 51965 ***