Comment 11 for bug 517021

Yes, mucku

Your solution worked in my laptop. It seems that ~/.local/share/gvfs-metadata/ folder contain metadata from network that I have connected with. The problems is, I only connected to those network once.

Nautilus/gvfsd seems to crawl any network (specially samba network) when I'm connected to the network in my office and in some hotspot area. When I back home, gvfsd try to update the metadata by reopen the samba network folder that of course not exist in my home network.

So, I suspect that this is the cause of gvfsd-metadata to taking whole CPU resource to try to find the 'missing' directory and read it's content to update the metadata. Deleting metadata files will make the gvfsd 'forget' those directories.