← Back to team overview

desktop-packages team mailing list archive

[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage

 

John Paul Adrian Glaubitz (glaubitz) what use do I have that this bug
might have been fixed around gvfs_1.22 when the Ubuntu 14.04.1 that I
currently use  uses gvfs (1.20.3-0ubuntu1) released 2015-02-02 and this
bug is still present in it?!

For those that need a temporary fix for this bug, use the

sudo chmod -x /usr/lib/gvfs/gvfsd-metadata (makes gvfs-metadata non
executable)

command, but be warned, after doing this nautilus tends to forget some
settings and tweaks. For instance, on my computer, the desktop icons ( I
have "show desktop icons" enabled) tend to be moved on the left side of
the screen (in random order) on each system restart (this will
definitely happen if you erased the file(s) in ~/.local/share/gvfs-
metadata).

The "fix" can be reversed with

sudo chmod +x /usr/lib/gvfs/gvfsd-metadata (makes gvfs-metadata
executable again).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/517021

Title:
  gvfsd-metadata causes 100% CPU usage

Status in gvfs package in Ubuntu:
  Confirmed
Status in gvfs package in Debian:
  Fix Released

Bug description:
  Binary package hint: gvfs

  My disk space was really full at one moment, no byte left free. People say, that does corrupt the files in the ~/.local/share/gvfs-metadata folder, so the gvfsd-metadata can't read it without being screwed up.
  Workaround: run "rm -rf ~/.local/share/gvfs-metadata"

  Expected results:
  gvfsd-metadata should be able to handle the no space left situation.

  
  --- Original description ---
  After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC.
  Using "top" i can see that "gvfsd-metadata" is using 100% CPU and when i kill it the computer stops "hanging". I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer).

  Please fix this because it is highly annyoing. Right now i am killing
  it every 20s with the watch command to be able to work at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions