nautilus eat memory, locks desktop

Thanks for your bug report. Please try to obtain a backtrace of the hang http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

This seems to be the same problem as in: 185483

I saw a similar scenario just now: I attempted to display the Properties dialog for a file on the desktop (to check how big it was).

No Properties window appeared, but after some time I discovered that a) no icons or files were displayed on the desktop (i.e., the desktop was not displaying correctly) and b), nautilus was using 90% of the CPU so the computer was practically blocked. Alas, I don't know how to reproduce this.

That's exactly the problem..

The eating of memory, And no response on the desktop.

And the high cpu.

On Feb 20, 2008 8:51 AM, Carsten Agger <agger@c.dk> wrote:

> This seems to be the same problem as in: 185483
>
> I saw a similar scenario just now: I attempted to display the Properties
> dialog for a file on the desktop (to check how big it was).
>
> No Properties window appeared, but after some time I discovered that a)
> no icons or files were displayed on the desktop (i.e., the desktop was
> not displaying correctly) and b), nautilus was using 90% of the CPU so
> the computer was practically blocked. Alas, I don't know how to
> reproduce this.
>
> --
> nautilus eat memory, locks desktop
> https://bugs.launchpad.net/bugs/187547
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!.

Pedro Villavicencio wrote:
> Closing this bug report as no further information has been provided.
> Please feel free to reopen this bug if you can provide the information
> asked for. Thanks!.
>

Seriously, how can you ask for a crash backtrace when this bug doesn't
cause GNOME or X to crash? No crash => No crash backtrace.

br
Carsten
--
http://www.modspil.k

This is so true...

No trace that I tell..

John

On Wed, Mar 19, 2008 at 11:59 AM, Carsten Agger <agger@c.dk> wrote:

> Pedro Villavicencio wrote:
> > Closing this bug report as no further information has been provided.
> > Please feel free to reopen this bug if you can provide the information
> > asked for. Thanks!.
> >
>
> Seriously, how can you ask for a crash backtrace when this bug doesn't
> cause GNOME or X to crash? No crash => No crash backtrace.
>
> br
> Carsten
> --
> http://www.modspil.k
>
> --
> nautilus eat memory, locks desktop
> https://bugs.launchpad.net/bugs/187547
> You received this bug notification because you are a direct subscriber
> of the bug.
>

You can get a backtrace of the hang anyways, just attach gdb to the process.

Pedro Villavicencio wrote:
> You can get a backtrace of the hang anyways, just attach gdb to the
> process.
>
OK, I can do this next time this behaviour, or if I find out how to
reproduce it.

br
Carsten

--
http://www.modspil.dk

I can confirm this bug, Its rather crippling...it can be reproduced by opening a nautilus window and changing directory by double clicking a folder.
The hang also occurs sporadically when there is an open nautilus window. When the hang occurs, it takes ~14 seconds to eat through my 4 Gb of ram, after which my computer becomes increasingly unresponsive.
I attached gdb to nautilus by the command:
gdb nautilus 7779
The only interesting message was:
0x00000000ffffe410 in ?? () from /lib64/ld-linux-x86-64.so.2
which occured before I induced the hang in nautilus
then obtained a backtrace after inducing the error.
sadly, the backtrace is identical to a backtrace performed when nautilus is not failing:
(gdb) bt
#0 0x00000000ffffe410 in ?? () from /lib64/ld-linux-x86-64.so.2
#1 0x00000001ffb782f8 in ?? ()
#2 0xf78bbc6700000004 in ?? ()
#3 0xf7ad7a1b00000000 in ?? ()
#4 0x00000001f7b4f248 in ?? ()
#5 0xffb7835800000004 in ?? ()
#6 0x080b7908f7adc176 in ?? ()
#7 0x0000000100000004 in ?? () from /lib64/ld-linux-x86-64.so.2
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

I'm running x86_64 on a fresh install (as of today)
If you need any more info, or did the debugging wrong, lemme know (I'm new at this)

the backtrace is of no use, you should install libglib2.0-0-dbgsym libgtk2.0-0-dbgsym nautilus-dbgsym and try to get a new one. Such issues can be due to a svg in the directory you open sometimes

You are correct. The problem only occurs when the directory being changed to contains an SVG. In my case, my home directory contained the SVG.

backtrace attached. Since no actual crash occurs, I enduced the error, then stopped the process and performed the backtrace.

attached backtrace

blarg, it looks like it was simply a malformed SVG in my case...no problems with other SVGs, and evince and inkscape both display the same behavior when opening the SVG in question. Its possible that jtilghman has a completely different issue, but mine is effectively resolved.

could you open a bug on librsvg attaching the file triggering the issue?

I confirm the original bugreport. Can easily reproduce it on current installation (nautilus 1:2.22.1-0ubuntu1) by cutting-and-pasting some files (esp. jpg images - no svg's in that folders!) around bunch of directories. Nautilus began consuming more and more memory, while eating about 80-90% cpu; if left up leads to fully inaccessible machine with oom-killer traces in syslog. After pkill'ing nautilus process, all files moved by last action in nautilus seem to be in their destination dir (that is nautilus starts leaking after actual file move/copy operations).

do you get the issue using any file or only some specific examples?

I made some experiments with some files having top running alongside and ready to fire `pkill nautilus`: looks like I found a testcase to reproduce this. Make a directory, put video file in mkv container (matroska) into it (mv file to that directory with shell) and watch for nautilus eating memory. It looks like this: file appears in directory, gnome-video-thumbnailer eats some cpu making its job, then movie thumbnail appears instead of standard videotape icon, and nautilus cpu usage begin to increase, as its memory consumption. If not killed, its residual memory goes up to all available, then virtual memory jumps up to 1 gib (I've got 1gib installed), everything else swaps out till system stops responding.

Tried this on different mkv files: with Xvid, h.264 video, different audiostreams (mp3, ac3), resolutions (nearly-vga to hdtv) -- all the same.

Just tried to attach strace to running (and leaking) nautilus. First and last 15 lines of strace output attached; total number of lines was > 100k (19Mb file).

P.S.: Note timestamps in attach -- total strace runtime was only about 9 seconds.

I confirm the bug.
Every time I download a big file (f.example .avi 700MB File) into desktop with firefox, when download finish, nautilus begin to eat memory, not more cpu, and when it's takes 80% of total amount of memory it crash and then restart the cicle.
When i move the file from desktop to my home folder nautilus stop eating memory, but it is very difficult because the system is very slow and not responding to mouse and keyborads very well.

Another thing,
the bug is present when i copy a big file into the desktop too, not only when downloading from internet by ff.

do you get the issue when not enabling the thumbnailing option? what zoom setting do you use?

Mmm, can i disable thumbnail view on desktop?
Zomm is 100% but it's refeered to nautilus icons view.

do you still get the issue? could you describe easy steps to trigger the bug?

I was running Linux Mint when the lock happened. I am trying to load Linux
Mint v5, i will let you know if it happens with this load.

Thanks,

JT

On Wed, Jun 25, 2008 at 9:09 AM, Sebastien Bacher <email address hidden> wrote:

> do you still get the issue? could you describe easy steps to trigger the
> bug?
>
> --
> nautilus eat memory, locks desktop
> https://bugs.launchpad.net/bugs/187547
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!.

I can reproduce this problem at will:

using nautilus 2.24.2 on fc10 (2.6.27.19)
Open any folder containing .avi files in "icon view" and watch resource meter. see memory usage going up to whatever. Exit nautilus. memory is released. Restart nautilus, select "list view" for the directory containing avi files and problem goes away! or reselect "icon view" to reproduce problem.

I can reliably reproduce this bug by viewing a folder with one or more large AVI files, in "Icon View", with "View Size" at 200% or greater. 100% or 150% "View Size" is no problem: nautilus idles and uses about 68M of virtual and 23M of resident memory. If I switch to 200% "View Size", it pegs one core at 100% usage and consumes 1G of virtual and resident memory. Trying to use nautilus at that point generally hangs it.

I'm running:
  Atom N330
  2G RAM

  Ubuntu 9.04 (netbook remix) 64bit
  Nautulis 2.26.2

Please let me know if I can provide any further information.

you should rather open a new bug than comment on a closed one

I am fine either way. What ever tracks it better.

On Mon, Jun 1, 2009 at 6:36 AM, Sebastien Bacher <email address hidden> wrote:

> you should rather open a new bug than comment on a closed one
>
> --
> nautilus eat memory, locks desktop
> https://bugs.launchpad.net/bugs/187547
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Got bit by this after moving files from my home dir to another disc.
I don't have any large files or images or svn's in my home directory, but I cannot now open it. Nautilus freezes and quickly eats up RAM. Other directories open fine. Sounds like a bug that manifests after some file ops have occurred - I don't think it is related to file content at all. It's a serious bug that is making me think of an alternative to Nautilus.

Well, I am just a user... So, fill out a bug report..

On Fri, Jun 26, 2009 at 4:02 PM, ticket <email address hidden>wrote:

> Got bit by this after moving files from my home dir to another disc.
> I don't have any large files or images or svn's in my home directory, but I
> cannot now open it. Nautilus freezes and quickly eats up RAM. Other
> directories open fine. Sounds like a bug that manifests after some file ops
> have occurred - I don't think it is related to file content at all. It's a
> serious bug that is making me think of an alternative to Nautilus.
>
> --
> nautilus eat memory, locks desktop
> https://bugs.launchpad.net/bugs/187547
> You received this bug notification because you are a direct subscriber
> of the bug.
>