cairo-dock-team team mailing list archive

[Pedro Villavicencio <pedro@xxxxxxxxxx>]

Thanks for the report, it has been some time without any response or
feedback in this bug report and we are wondering if this is still an
issue for you with the latest release of Ubuntu the Natty Narwhal, May
you please test with that version and comment back if you're still
having or not the issue? Please have a look at
http://www.ubuntu.com/download to know how to install that version.
Thanks in advance and sorry for the late response.

** Changed in: gvfs (Ubuntu)
   Importance: Undecided => Low

** Changed in: gvfs (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Cairo-
Dock Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/662705

Title:
  gvfsd-trash fills up memory

Status in “gvfs” package in Ubuntu:
  Incomplete

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

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