← Back to team overview

desktop-packages team mailing list archive

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


Also, I don;t think that the current incarnation of this bug is filling
my HDD. When I open the ~/.local/share/gvfs-metadata folder in the file
browser it is evident that a few files are constantly being generated
and then erased ad nauseam. So there is no disk space eating problem,
just the HDD (and laptop battery) straining problem.

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.

  gvfsd-metadata causes 100% CPU usage

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

Bug description:
  Binary package hint: gvfs

  Failure to write metadata results in an infinite loop that keeps
  trying to write, thousands of times per second.

  Steps to reproduce:
  1. Open Firefox
  2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file

  (There are other ways to run into this problem, e.g. disk full or
  other error situations. data: URLs are just the easiest way to

  Actual result:
  - File is saved
  - 100% CPU
  - Extremely high number of file operations by gvfs - billions
  - Never stops

  Expected result:
  Failure to write metadata should just fail, not try again

  Patch available and accepted by GNOME

  --- 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: