Bug 154929 - Samba KIO slave uses high CPU load, and transfer stalls after a while when copying large files.
Summary: Samba KIO slave uses high CPU load, and transfer stalls after a while when co...
Status: RESOLVED WORKSFORME
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: smb (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-01 17:18 UTC by Rob Scheepmaker
Modified: 2008-02-02 12:29 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rob Scheepmaker 2008-01-01 17:18:16 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          g++ (GCC) 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) 
OS:                Linux

When I use konqueror or dolphin to transfer one or more files, the transfer starts at the usual, to be expected speed (around 6/7 MB/s). However, after transferring around 60-70 MB, the transfer suddenly starts slowing down, untill it's stalled. It never continues, and at that moment konqueror or dolphin (I assume this is the same for any KIO aware app) start using 60-70% CPU untill I cancell the transfer. 
I have been able to reproduce this bug every time I tried. When I log in into a kde3 session on the same machine, I can transfer files normally using the samba KIO slave.
Please feel free to ask for more information, I don't really now what info can be usefull, but I'm willing to help. I have compiled from SVN, and I'm willing to recompile to verify if to bug has been solved.
Comment 1 Rob Scheepmaker 2008-01-02 14:41:08 UTC
To make this clear: this bug occurs only on kde4, and not on kde3.
Comment 2 Rob Scheepmaker 2008-02-02 12:29:50 UTC
I recently noticed this bugreport:

http://bugs.kde.org/show_bug.cgi?id=156259

Since it got solved this bug also disappears, since it's probably the same bug.