After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 302879 - gnome-vfs-daemon, gnome-panel and nautilus hog CPU after file operations
gnome-vfs-daemon, gnome-panel and nautilus hog CPU after file operations
Status: RESOLVED INCOMPLETE
Product: gnome-vfs
Classification: Deprecated
Component: Module: file
1.0.5
Other All
: Normal major
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
Depends on:
Blocks:
 
 
Reported: 2005-05-03 16:56 UTC by Oscar Valdez
Modified: 2006-05-01 00:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Oscar Valdez 2005-05-03 16:56:19 UTC
Please describe the problem:
After using the File Selection dialog, CPU usage by gnome-vfs-daemon,
gnome-panel and nautilus shoots up close to 100%, making the system unusable.

Steps to reproduce:
1. Open File Selection dialog from any GNOME application.
2. Select File, or close dialog without selecting file
3. CPU usage by gnome-vfs-daemon, gnome-panel and nautilus shoots up close to
100%, as reported by top.


Actual results:
Desktop slows to a crawl.

Expected results:
System continues functioning normally.

Does this happen every time?
Yes

Other information:
Running Fedora Core 3
Comment 1 Christian Kirbach 2005-07-14 20:38:03 UTC
Thanks for taking the time to report this bug. This bug report isn't very useful 
because it doesn't describe the bug well.
What versions of Gnome, gtk are you using?
Comment 2 Sebastien Bacher 2005-07-24 20:00:53 UTC
no reply, bug closed. Feel free to reopen with the asked informations if that's
still an issue for you
Comment 3 Mike Nolta 2005-08-08 22:09:28 UTC
I'm having the same problem as Oscar, and I'm also running Fedora Core 3 (FC3).
My home directory is nfs-mounted, which may be the cause. Here's another report
of this bug by someone running FC3+NFS:

http://mail.gnome.org/archives/gnome-vfs-list/2005-May/msg00002.html
Comment 4 Oscar Valdez 2005-08-08 23:36:42 UTC
The way I've "solved" the problem is by deleting the users' ~/.gconf and
~/.gconfd directories. New ones get created upon the users' next login, and the
system is usable once more.

For the record, I've been using gtk+-1.2.10 and gnome-desktop-2.8.0
Comment 5 Ian Perryman 2005-09-13 14:39:06 UTC
I see this same behaviour using FC3.  My home is nfs mounted as well.  Not sure
what additional information you might require.  I am putting my nfs mount for
home dir in case that is of help.
From /etc/fstab....
otc-blue:/home       /home         nfs 
tcp,nfsvers=3,bg,hard,intr,noatime,rsize=32768,wsize=32768,actimeo=30,timeo=600,retrans=13
0 0



Here are some packages reported by rpm -qa | grep gnome 

gnome-vfs2-2.8.2-8
gnome-panel-2.8.1-3
gnome-applets-2.8.0-5
gnome-vfs2-smb-2.8.2-8
gnome-vfs-1.0.5-21

Here is top output when bug has been encountered.  Note almost all cpu being
hogged by gnome-settings-daemon, gnome-vfs-daemon, and gnome-panel, roughly in
thirds.

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 4404 iperryma  25   0 20028 6812 5440 S 29.9  1.3   9:58.67 gnome-settings-
 4459 iperryma  25   0 21680 3004 2648 R 27.3  0.6   9:53.27 gnome-vfs-daemo
 4449 iperryma  25   0 25304  11m 7780 R 27.0  2.3  10:17.74 gnome-panel


Ian
Comment 6 Rithin Shetty 2005-10-13 01:52:00 UTC
I have been observing the same behavior with gnome-settings-.  I use FC 4 with
all the default settings. Please let me know if you need more info, my system
remains up and running always. So if you need any info I can try. Here is the
output from the "top" command.

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 4990 rithin    25   0 20736  968  652 S 99.8  0.1   7964:53 gnome-settings-
28367 rithin    15   0  177m 122m  21m S 13.9 12.3  95:10.94 firefox-bin
 3585 root      15   0  386m  69m 9.8m S  7.3  6.9   1878:34 X
 5043 rithin    25  10 36140 5472 3032 S  0.7  0.5  21:49.59 rhn-applet-gui
13497 rithin    15   0 33848  12m 8288 S  0.7  1.3   0:04.60 realplay.bin
13909 rithin    16   0  2284 1156  868 R  0.7  0.1   0:00.75 top
 5072 rithin    15   0 76048  50m 4880 S  0.3  5.1  13:34.34 gnome-terminal
Comment 7 Jonathan Brooks 2005-10-15 11:56:19 UTC
HI,

I see the same problem with SuSE 10 - which uses Gnome 2.12. In my situation I
have both old user dirs (from earlier versions of SuSE) and NFS mounted home
dirs. I see either nautilus or gnome-panel utilising ~100% CPU (with top). So
the solution is to delete ~/.gconf and /.gconfd??

Incidentally, just yesterday I was getting NFS related error messages saying
that TCP was unavailable and the NFS client was switching to use UDP instead.
Is this related?

FYI the relevant installed packages on my machine are:
gnome-panel-2.12.0-5
gnome-vfs2-2.12.0-9.2
gnome-vfs2-32bit-2.12.0-9.2
nautilus-2.12.0-7
nautilus-32bit-2.12.0-7

Best wishes,

Jon.
Comment 8 Russ Weeks 2005-11-10 23:56:48 UTC
I also encounter this problem.  Haven't narrowed down steps to reproduce yet. 
My installed packages are:

[rweeks@rweeks-lin:~]rpm -qa | grep "gnome\|nautilus" | sort
gnome2-SuSE-10.0-9
gnome2-user-docs-2.8.1-5
gnome-applets-2.12.0-3
gnome-audio-2.0.0-120
gnome-backgrounds-2.12.0-3
gnome-bluetooth-0.5.1-14
gnome-cups-manager-0.31-3
gnome-desktop-2.12.0-3
gnome-doc-utils-0.4.0-2
gnome-filesystem-0.1-230
gnome-games-2.12.0-3
gnome-icon-theme-2.12.0-3
gnome-keyring-0.4.4-3
gnome-keyring-manager-2.12.0-2
gnome-mag-0.12.1-3
gnome-media-2.12.0-3
gnomemeeting-1.2.2-3
gnome-menus-2.12.0-4
gnome-mime-data-2.4.2-7
gnome-netstatus-2.12.0-2
gnome-nettool-1.4.0-3
gnome-panel-2.12.0-5
gnome-pilot-2.0.13-7
gnome-printer-add-1.0.0-3
gnome-screensaver-0.0.13-2
gnome-session-2.12.0-3
gnome-speech-0.3.7-5
gnome-spell2-1.0.6-7
gnome-system-monitor-2.12.0-3
gnome-terminal-2.12.0-3
gnome-themes-2.12.0-5
gnome-utils-2.12.0-3
gnome-vfs2-2.12.0-9.2
gnome-volume-manager-1.5.1-3
hal-gnome-0.5.4-6.2
libgail-gnome-1.1.1-3
libgnome-2.12.0.1-2
libgnomecanvas-2.12.0-2
libgnomecups-0.2.2-0.2
libgnomedb-1.3.91-5
libgnomeprint-2.12.1-0.3
libgnomeprintui-2.12.1-2.2
libgnomesu-1.0.0-3.2
libgnomeui-2.12.0-3
libgsf-gnome-1.12.1-3
nautilus-2.12.0-7
nautilus-cd-burner-2.12.0-4
nautilus-open-terminal-0.4-3
nautilus-sendto-0.4-3
OpenOffice_org-gnome-2.0.0-1.2
python-gnome-2.12.0-3
python-gnome-extras-2.11.3-3
xmms-gnome2-0-510

Since the information that Sebastien and Christian asked for has been provided,
I believe this bug should be re-opened.
Comment 9 Rithin Shetty 2005-11-18 17:59:52 UTC
Since so many of us are seeing this bug, We should reopen this bug for gnome
version 2.10.
 
Other version information:

gnome-vfs2-2.10.0-5
gnome-panel-2.10.1-10
Comment 10 Leonardo 2006-02-10 22:49:19 UTC
I experience the same bug on version 2.12. I noticed this bug from 2.8 and so on. I've changed the entire gnome environment, but the problem presist. 

now i use these packages, installed on a slackware system and compiled by the gware team:

at-spi-1.6.6-i486-1gwE
atk-1.10.3-i486-1gwE
bug-buddy-2.12.0-i486-1gwE
cairo-1.0.2-i486-1gwE
control-center-2.12.0-i486-2gwE
dasher-3.2.18-i486-1gwE
dbus-0.50-i486-1gwE
desktop-file-utils-0.10-i486-1gwE
eel-2.12.0-i486-1gwE
eog-2.12.0-i486-1gwE
epiphany-1.8.2-i486-1gwE
epiphany-extensions-1.8.0-i486-1gwE
evince-0.4.0-i486-1gwE
evolution-2.4.0-i486-1gwE
evolution-data-server-1.4.0-i486-1gwE
evolution-webcal-2.4.0.1-i486-1gwE
fam-2.7.0-i486-1gwE
file-roller-2.12.0-i486-1gwE
gail-1.8.5-i486-1gwE
gal-2.5.3-i486-1gwE
gcalctool-5.7.11-i486-1gwE
gconf-2.12.0-i486-1gwE
gconf-editor-2.12.0-i486-1gwE
gdm-2.8.0.4-i486-1gwE
gedit-2.12.1-i486-1gwE
ggv-2.8.5-i486-1gwE
gksu-1.3.4-i486-1gwE
glib2-2.8.4-i486-1gwE
glibmm-2.8.0-i486-1gwE
gnome-applets-2.12.0-i486-1gwE
gnome-audio-2.0.0-noarch-1gwE
gnome-backgrounds-2.12.0-i486-1gwE
gnome-common-2.11.0-i486-1gwE
gnome-cups-manager-0.30-i486-1gwE
gnome-desktop-2.12.0-i486-1gwE
gnome-doc-utils-0.4.0-noarch-1gwE
gnome-games-2.12.1-i486-1gwE
gnome-games-extra-data-2.12.0-noarch-1gwE
gnome-icon-theme-2.12.0-noarch-1gwE
gnome-keyring-0.4.4-i486-1gwE
gnome-keyring-manager-2.12.0-i486-1gwE
gnome-mag-0.12.1-i486-1gwE
gnome-media-2.12.0-i486-1gwE
gnome-menus-2.12.0-i486-1gwE
gnome-mime-data-2.4.2-noarch-1gwE
gnome-netstatus-2.12.0-i486-1gwE
gnome-nettool-1.4.1-i486-1gwE
gnome-panel-2.12.0-i486-1gwE
gnome-pilot-2.0.13-i486-1gwE
gnome-pilot-conduits-2.0.13-i486-1gwE
gnome-python-2.12.0-i486-1gwE
gnome-session-2.12.0-i486-1gwE
gnome-speech-0.3.7-i486-1gwE
gnome-spell-1.0.6-i486-1gwE
gnome-system-monitor-2.12.0-i486-1gwE
gnome-system-tools-1.4.0-i486-1gwE
gnome-terminal-2.12.0-i486-1gwE
gnome-themes-2.12.0-noarch-1gwE
gnome-themes-extras-0.8.1-i486-1gwE
gnome-utils-2.12.0-i486-1gwE
gnome-vfs-2.12.0-i486-1gwE
gnome-volume-manager-1.5.1-i486-1gwE
gnome2-user-docs-2.8.1-noarch-1gwE
gnopernicus-0.11.6-i486-1gwE
gnutls-1.2.6-i486-1gwE
gob-2.0.12-i486-1gwE
gok-1.0.5-i486-1gwE
gpdf-2.10.0-i486-1gwE
gst-ffmpeg-0.8.6-i486-1gwE
gst-plugins-0.8.11-i486-1gwE
gstreamer-0.8.11-i486-1gwE
gtk+2-2.8.9-i486-1gwE
gtk-engines-2.6.5-i486-1gwE
gtkhtml-3.8.0-i486-1gwE
gtkmm-2.8.0-i486-1gwE
gtksourceview-1.4.1-i486-1gwE
gucharmap-1.4.3-i486-1gwE
hal-0.5.4-i486-2gwE
hicolor-icon-theme-0.5-noarch-1gwE
howl-1.0.0-i486-1gwE
intltool-0.34.1-noarch-1gwE
iso-codes-0.42-noarch-1gwE
krb5-1.4.2-i486-1gwE
libbonobo-2.10.1-i486-1gwE
libbonoboui-2.10.1-i486-1gwE
libcap-1.10-i486-1gwE
libcroco-0.6.0-i486-1gwE
libgail-gnome-1.1.1-i486-1gwE
libgcrypt-1.2.1-i486-1gwE
libgksu1.2-1.3.3-i486-1gwE
libgksuui1.0-1.0.6-i486-1gwE
libglade-2.5.1-i486-1gwE
libgnome-2.12.0.1-i486-1gwE
libgnomecanvas-2.12.0-i486-1gwE
libgnomecups-0.2.1-i486-1gwE
libgnomeprint-2.11.0-i486-1gwE
libgnomeprintui-2.11.0-i486-1gwE
libgnomeui-2.12.0-i486-1gwE
libgpg-error-1.0-i486-1gwE
libgtop-2.12.0-i486-1gwE
libidl-0.8.6-i486-1gwE
libmusicbrainz-2.1.1-i486-1gwE
librsvg-2.11.1-i486-1gwE
libsigc++-2.0.16-i486-1gwE
libsoup-2.2.6.1-i486-1gwE
libtasn1-0.2.17-i486-1gwE
libwnck-2.12.0-i486-1gwE
libxklavier-2.0-i486-1gwE
metacity-2.12.1-i486-1gwE
nautilus-2.12.0-i486-1gwE
nautilus-cd-burner-2.12.0-i486-1gwE
opencdk-0.5.8-i486-1gwE
openh323-1.15.6-i486-1gwE
openldap-2.3.7-i486-1gwE
orbit2-2.12.4-i486-1gwE
libxklavier-2.0-i486-1gwE
metacity-2.12.1-i486-1gwE
nautilus-2.12.0-i486-1gwE
nautilus-cd-burner-2.12.0-i486-1gwE
opencdk-0.5.8-i486-1gwE
openh323-1.15.6-i486-1gwE
openldap-2.3.7-i486-1gwE
orbit2-2.12.4-i486-1gwE
pango-1.10.2-i486-1gwE
poppler-0.4.2-i486-1gwE
pwlib-1.8.7-i486-1gwE
pycairo-1.0.0-i486-1gwE
pygtk-2.8.0-i486-1gwE
pyorbit-2.0.1-i486-1gwE
scrollkeeper-0.3.14-i486-1gwE
sound-juicer-2.12.2-i486-1gwE
system-tools-backends-1.4.0-noarch-2gwE
totem-1.2.0-i686-2gwE
vino-2.12.0-i486-1gwE
vte-0.11.15-i486-1gwE
yelp-2.12.0-i486-1gwE
zenity-2.12.0-i486-1gwE

when i try to start nautilus, the gnome-vfs-daemon increase his cpu and memory usage. Then, seems that it crash, but nautilus restart it, so the process retry to use 100% cpu and memory.

i've tried to delete some config folders, such as .gconf* .gnome* and /tmp/*orbit, but nothing different happens. 

I've also tried to restart hal and dbus. so, when i launch nautilus, it hangs up like waiting for something, not using cpu nor memory. Using option -c give this result: 

running nautilus_self_check_file_utilities
running nautilus_self_check_file_operations
running nautilus_self_check_directory

then nautilus wait. 

Comment 11 A.Wagner 2006-02-13 07:00:42 UTC
i have the same problem (gnome 2.12 on suse 10.0) additionally my swap is filled slowly but continuously until i kill the gnome-vfs-deamon. after the weekend it was 500mb swap wich was cleared after killing the deamon.

A.Wagner
Comment 12 Andre Costa 2006-03-08 18:19:49 UTC
I've been experiencing this as well, on my up-to-date FC4 box. As I write this message, both my CPUs are alternating 100% CPU, and the top CPU eater is gnome-vfs-daemon.

GNOME version is: 2.10.0
kernel version is: 2.6.15-1.1833_FC4smp

I ran strace on gnome-vfs-daemon process and this came up:

poll([{fd=19, events=POLLIN}, {fd=21, events=POLLIN|POLLPRI}, {fd=23, events=POLLIN}, {fd=25, events=POLLIN}, {fd=26, events=POLLIN, revents=POLLNVAL}], 5, -1) = 1
poll([{fd=19, events=POLLIN}, {fd=21, events=POLLIN|POLLPRI}, {fd=23, events=POLLIN}, {fd=25, events=POLLIN}, {fd=26, events=POLLIN, revents=POLLNVAL}], 5, -1) = 1
poll([{fd=19, events=POLLIN}, {fd=21, events=POLLIN|POLLPRI}, {fd=23, events=POLLIN}, {fd=25, events=POLLIN}, {fd=26, events=POLLIN, revents=POLLNVAL}], 5, -1) = 1
poll([{fd=19, events=POLLIN}, {fd=21, events=POLLIN|POLLPRI}, {fd=23, events=POLLIN}, {fd=25, events=POLLIN}, {fd=26, events=POLLIN, revents=POLLNVAL}], 5, -1) = 1
poll([{fd=19, events=POLLIN}, {fd=21, events=POLLIN|POLLPRI}, {fd=23, events=POLLIN}, {fd=25, events=POLLIN}, {fd=26, events=POLLIN, revents=POLLNVAL}], 5, -1) = 1
poll([{fd=19, events=POLLIN}, {fd=21, events=POLLIN|POLLPRI}, {fd=23, events=POLLIN}, {fd=25, events=POLLIN}, {fd=26, events=POLLIN, revents=POLLNVAL}], 5, -1) = 1
poll([{fd=19, events=POLLIN}, {fd=21, events=POLLIN|POLLPRI}, {fd=23, events=POLLIN}, {fd=25, events=POLLIN}, {fd=26, events=POLLIN, revents=POLLNVAL}], 5, -1) = 1
poll([{fd=19, events=POLLIN}, {fd=21, events=POLLIN|POLLPRI}, {fd=23, events=POLLIN}, {fd=25, events=POLLIN}, {fd=26, events=POLLIN, revents=POLLNVAL}], 5, -1) = 1
poll([{fd=19, events=POLLIN}, {fd=21, events=POLLIN|POLLPRI}, {fd=23, events=POLLIN}, {fd=25, events=POLLIN}, {fd=26, events=POLLIN, revents=POLLNVAL}], 5, -1) = 1
...

(it kept repeating this on and on)

Running strace with -c parameter on the same process yielded this:

strace -p 30211 -c
Process 30211 attached - interrupt to quit
Process 30211 detached
% time     seconds  usecs/call     calls    errors syscall
------ ----------- ----------- --------- --------- ----------------
100.00    0.304120           6     51743           poll
------ ----------- ----------- --------- --------- ----------------
100.00    0.304120                 51743           total

So, it seems gnome-vfs-daemon was stuck on the poll() call on a tight loop.

Additional info:

- problem is intermittent
- I don't run GNOME desktop (I use fluxbox), but I do run gnome-panel. Also, I open nautilus file browser (with --no-desktop) every once in a while.
- today I opened nautilus to access a USB pendrive. I umounted the pendrive before unplugging it
- home sits on a NFS-mounted partition
- coincidence or not, after I opened gnome-panel's main menu, CPU usage dropped back to normal

HTH narrow down the problem.

If you need additional info, please let me know.
Comment 13 Leonardo 2006-05-01 00:52:29 UTC
i've tried to recompile gnome-vfs 2.12.2 and use gdb. Seems that gnome-vfs-daemon have an infinte loop recalling  giop_send_buffer_append_aligned()  from /usr/lib/libORBit-2.so.0. Here is the info stack from gdb:

(gdb) info stack
  • #0 giop_send_buffer_append_aligned
    from /usr/lib/libORBit-2.so.0
  • #1 ORBit_marshal_value
    from /usr/lib/libORBit-2.so.0
  • #2 ORBit_marshal_value
    from /usr/lib/libORBit-2.so.0
  • #3 ORBit_marshal_value
    from /usr/lib/libORBit-2.so.0
  • #4 ORBit_marshal_value
    from /usr/lib/libORBit-2.so.0
  • #5 ORBit_marshal_arg
    from /usr/lib/libORBit-2.so.0
  • #6 ORBit_small_invoke_adaptor
    from /usr/lib/libORBit-2.so.0
  • #7 ORBit_recv_buffer_return_sys_exception
    from /usr/lib/libORBit-2.so.0
  • #8 ORBit_recv_buffer_return_sys_exception
    from /usr/lib/libORBit-2.so.0
  • #9 giop_thread_queue_process
    from /usr/lib/libORBit-2.so.0
  • #10 giop_thread_same_key
    from /usr/lib/libORBit-2.so.0
  • #11 link_servers_move_io_T
    from /usr/lib/libORBit-2.so.0
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_acquire
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #15 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #16 main
    at gnome-vfs-daemon.c line 618

line 618 in gnome-vfs-daemon.c call the bonobo_main(), in this code:



factory = bonobo_generic_factory_new ("OAFIID:GNOME_VFS_Daemon_Factory",
				      gnome_vfs_daemon_factory,
				      NULL);
if (factory) {
	bonobo_main ();   <-------------------- HERE IS!
	
	bonobo_object_unref (BONOBO_OBJECT (factory));
	if (the_daemon) {
		bonobo_object_set_immortal (BONOBO_OBJECT (the_daemon), FALSE);
		bonobo_object_unref (BONOBO_OBJECT (the_daemon));
	}
	gnome_vfs_shutdown();
	gconf_debug_shutdown();
	return bonobo_debug_shutdown ();
} else {
	g_warning ("Failed to create factory\n");
	return 1;
}


seems that gnome-vfs-daemon remain in this function that try to initialize bonobo. So, maybe is a problem within orbit2? I have to do some tests.