Bug 317612 - CPU to 100% when copying lot of files to a shared folder
Summary: CPU to 100% when copying lot of files to a shared folder
Status: RESOLVED WORKSFORME
Alias: None
Product: kio
Classification: Unmaintained
Component: smb (show other bugs)
Version: 4.10.1
Platform: Arch Linux Linux
: NOR grave
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2013-03-30 16:40 UTC by Sergio García
Modified: 2018-10-27 03:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sergio García 2013-03-30 16:40:33 UTC
After some time, when copying lots of big files from my local computer to a shared network drive, my computer freezes completely. If I execute the "top" command I see how the longer the copying process lasts, the more CPU resources a process "kswapd0" use. The last time I tried, it passed only 5 minutes since the resource usage of "kswapd0" began to use all my CPU. I installed nautilus to check if this behavior also appeared (using other processes) but it has been copying non-stop smoothly for 2 days.

Reproducible: Always

Steps to Reproduce:
1. Attach directly (not attached to other computer) a network drive using samba.
2. Move a folder plenty of big files (movies, for example) to the remote.
3. Keep track of the CPU usage.
Actual Results:  
100% of CPU usage.

Expected Results:  
The files should be moved to the network folder and the unique resource intensively used should be networking.
Comment 1 Dawit Alemayehu 2013-06-06 04:22:25 UTC
kswapd0 is not a KDE application. It is a Linux kernel module responsible for managing swap space ; so  unless you run out of memory I do not see why and how that process starts eating up all your CPU cycles. Is there sufficient memory on your machine ?
Comment 2 Dawit Alemayehu 2013-06-06 04:29:10 UTC
Also see the same reports from others here: https://bbs.archlinux.org/viewtopic.php?id=144702
Comment 3 Dawit Alemayehu 2013-06-30 00:27:01 UTC
comment #1.
Comment 4 Andrew Crouthamel 2018-09-24 02:00:20 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-27 03:54:40 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!