desktop-packages team mailing list archive

[MFeif <matt.feifarek@xxxxxxxxx>]

Sigh.

I let it run for about 15 minutes. I tried to "use" it, but like I said,
it takes about 1m just to open a window. So I didn't use it "much".

It's not possible to monitor the resource usage of nautilus when it's
running inside of valgrind, because it's not in the System Monitor
anymore... a 500MB task that wraps it up is instead. What's happening
inside of this appears to be opaque to the tools I have.

I have about 15 items on the "desktop"... one perhaps clue is that I
have the "desktop" set to ~/ via the gconf settings. This means that
there are very many ".dotfiles" which are hidden to nautilus as it
paints the desktop.

There is one .png on the desk, but it hasn't updated in weeks. I'm not
downloading anything there (I have Downloads, ala Ubuntu standard).

To pursue this line of reasoning, I've turned off everything on the
"Preview" tab of the nautilus preferences... removed most of the files
from the "~" to clean the "desktop" and restarted nautilus. I'll watch
it for a while and report back.

One probably irrelevant thing: I see TONS of these in .xsession-errors:
"(nautilus:18652): Gtk-CRITICAL **: gtk_container_foreach: assertion
`GTK_IS_CONTAINER (container)' failed"

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

Title:
  nautilus memory leak

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  There are other bug reports with this description, but they are either
  3-4 years old, or closed, or invalid, or expired.

  I'm not doing anything exotic, but after about an hour or two of using
  my system (not even copying or moving files, or thumbnailing, or...)
  memory usage in nautilus goes up to 1.4G or so. When I kill this task,
  re-launch nautilus, it sits happily on just a few hundred meg... and
  then begins to grow again.

  It also takes a LONG time to start up, and the system is very
  unresponsive meanwhile... like 20 seconds. This may be a useful clue?

  I tried to do a valgrind report, but it makes nautilus so slow as to
  be unusable -- like 2 minutes to open a folder on the desktop... so I
  couldn't exactly "use it normally" to get a good log. Nonetheless,
  here's a log I did capture.

  I trust that the data captured by ubuntu-bug will have my library
  versions, cpu type, RAM info, etc. Please let me know what else I can
  provide. Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: nautilus 1:3.2.1-0ubuntu3.1
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 14 15:51:46 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110802.1)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to oneiric on 2011-08-17 (88 days ago)

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