GNOME Bugzilla – Bug 111689
100% CPU usage on FAM monitored windows
Last modified: 2005-01-03 13:32:42 UTC
I quite often leave Nautilus open on my /mnt/storage/Unsorted director, and at the same time leave d4x downloading to that directory, After a few minutes my cpu usage is averaging 30-40 percent. After I leave it for a long time (overnight usually) it has taken 100% cpu usage, and has to be killed. I believe the two are related. * The directory has 71 items in it. * It does not seem to have to be in view. * If i remove fam (which itself takes about 2%) it does not seem to do it. * /mnt/storage is mounted via NFS
Does this still happen in recent versions?
Yes it does, I'm running 2.4 (debian testing)
Reopening then.
Reopening, setting version->2.4.x and updating summary to better reflect the issue.
Debian used to provide fam with default config to inetd, but this mode seems cause some problem and has just been removed from unstable. Perhaps it's the reason of the bug. Could you look the mode, and if it's "inetd" switch to "standalone" (dpkg-reconfigure fam) to test if it solve the bug ? Thanks
Slight issue testing it, I've just switched to Fedora. I'm getting a new HDD soon and will install debian on that (im getting pissed off with having to find software instead of apt-get anyway). I'll let you know in about a week or two.
it is the same with fam running standalone. you get the same problem without beeing able to close the window if you download something to the desktop. together with thumbnail preview for video clips it tries to regenerates the image all the time.
Is the process using all the CPU a nautilus process or a thumbnailer process (such as totem-video-thumbnailer)?
OK the 100% usage problem has gone, however if your renaming a file while your typing it continually stops editing (as if you'd pressed enter). I assume FAM causes Nautilus to re-draw the screen type of thing. Summary While downloading into directory (this is actually the server downloading, while im on a diff computer) 1. press F2 on a file 2. start typing, 3, pretty soon you will lose the editing, as if you'd pressed enter (should be about every 1-3 seconds. Tested on Ubuntu
the rename bug is a duplicate of #158366
*** This bug has been marked as a duplicate of 158366 ***