Comment 18 for bug 890441

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"