GNOME Bugzilla – Bug 332517
Copying takes up 100% CPU usage
Last modified: 2014-01-22 10:42:27 UTC
Please describe the problem: When I start to copy something over 100MB, i get 100% cpu usage, the mouse cursor get very very slow, the system also becomes very slow, the copying process is OK, but i can't do (almost) anything else. This happens when i copy from a CD, FTP, HDD. Steps to reproduce: 1. 2. 3. Actual results: I get 100% cpu usage and a very slow system. Expected results: I expect to get 20-30-may-be-40-50% cpu usage, but NOT 100% Does this happen every time? Yes. Other information: I use Ubuntu 5.10, FAT32, EXT3, RaiserFS, copying on all of these file systems I get the same result.
I forgot to mention that my pc has: celeron@700mhz, 256mb ram, seagate barracuda 40gb hdd, and i use xfce.
I can copy 60 MB files without any performance loss. This is 500mhz AMD K6, same RAM, seagate HD, all rather old stuff. On wmaker, xorg, FAMD enabled, kernel 2.6.13. I suggest you check the new 1.2.0 snapshot and try to figure out what's slowing your box down, eg by commandline tools strace and top, and some comparisons w/o FAM, and with other filemanagers (especially gnome ones like nautilus).
This bug happens under the following conditions: 1. Both sides display the same directory 2. "famd" is active. 3. Copying a very big file from one side to the other (to the same directory but with different file name). CPU usage goes quickly to 100%, but it is "famd" which hogs the CPU, not gnome-commander. However, this might be due to a bad handling of "famd" signals in gnome-commander.
Have you tried with Gamin instead of Fam ? If the behaviour is the same with both, maybe it's GNOME Commander's fault. If not, blame Fam ;).
I installed 1.2.0 and walked exactly the steps Assaf talked above. With or without famd running, anyway, copying a 120M file took about 50 % CPU. Still the same old hardware. However, i can't deinstall libfam easily, too many other apps depend on it....This is Linux 2.6.18-1 (custom) entertaining a Debian GNU/Linux 4.0 (libgnomevfs2-0 2.14.2-4). If this error depends on some lib version or system setting, it's not necessarily a gcmd bug at all. We would need more examples, reproducing it for a 1.3 devel version would be especially interesting.
I can confirm such a bug in ver 1.2.4
I tried to reproduce the described behavior with the current development version 1.3, which will be stabilized soon. The CPU usage was less than 20% in my case. As the version for which this bug report was opened is very old now, I mark the bug as obsolete.