gvfsd-trash fills up memory
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
Binary package hint: gvfs
gvfsd-trash process multiply in memory and cause Cairo Dock to inflate its memory usage up to the maximum of available memory (3Gb) before drastically slowing down the host since the swap goes crazy under the load. Happens both using regular and OpenGL Cairo Dock versions.
Ubuntu 9.10 (x64) - kernel 2.6.31-22-generic - gvfs package 1.4.1-0ubuntu1 - GNOME 2.28.1 - Cairo Dock version 2.2.0-4
What I noticed: Cairo-dock icon could not report the dust bin to be filled (ie it kept showing the empty bin icon). In fact, my dust bin contained 8.9Gb of deleted files.
Killing the Cairo Dock process solved the bad host responsiveness. Emptying the dust bin with Nautilus solved the rest of the bug. Restarting Cairo-dock after that makes the whole system behave normally.
Noob conclusion: there's a bug in gvfs-trash causing it to panic when the dust bin gets severly loaded.
Extra: this never occured before despite the fact I had a dust bin containing even more than 8.9Gb. Problem *seems* to have raised with the latest kernel update.
Hope this helps
Hi, enumerate_ children with G_FILE_ QUERY_INFO_ NOFOLLOW_ SYMLINKS.
I can add the following information:
the dock browses recursively the URI trash:/ and gets the size of each file, using g_file_
I've personnally noticed that the whole process takes a lot of time when there are a lot of files, whereas the more basic method (using fopen and fstat) is much faster and gives the same result (I don't have network volumes).
Thanks for your concern.