nautilus stoping responding then opening directory witch contains 1600 photos. After update 16 Sept.

[avinas]

Binary package hint: nautilus

After Gutsy update of 18 September 2007. Nautilus is stopping responding (occasionally) then I was opening large subdirectory. Today I left system in this stage for a few hours. After that nautilus still not responding. System monitor indicated that nautilus used 1h50min processor time and was still eating 50% of processor resources(actualy 100% of one processor).

ProblemType: Bug
Architecture: i386
Date: Thu Sep 20 16:06:48 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.20.0-0ubuntu1
PackageArchitecture: i386
ProcCmdline: nautilus --sm-client-id 1021994cd6000119028819400000064210002 --screen 0
ProcCwd: /home/vilius
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
Uname: Linux neidomus 2.6.22-11-generic #1 SMP Mon Sep 17 03:45:58 GMT 2007 i686 GNU/Linux

[Pedro Villavicencio (pedro)]

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

[mdiorio (max-advantechcny)]

I'm seeing nautilus take 50% of my CPU (100% of my 2nd core) as well, although I'm not having any problems with anything not responding. It does seem that programs are opening slower on Gutsy than they did on Feisty though.

Running on Intel Core2Duo E4400.

[Luciano Panepucci (lpanebr)]

I moved to gutsy making a fresh install and now I'am having a similar issue that I do not remember having on Feisty:

When I open a directory with many files (700 pitctures in this case) Nautilus grays out for 30 seconds while "Loading..." the contents. However, in my case it comes back with the file list after those killer seconds.

This gray out only seems to happen while on the LIST VIEW any other open Nautilus windows gray out at the same time.

The backtrace I attached does not seem to help since Nautilus does not really crash. It only hangs for a while.. If there's another way to get a backtrace during the hang please tell me.

[Pedro Villavicencio (pedro)]

Thanks but the trace isn't really useful, please try to obtain a new one and re open the bug report. thanks.

[Luciano Panepucci (lpanebr)]

But nautilus does not crash. It only hangs for many seconds. I did not find info on how to obtain a trace during the hang? Can you give me some info on that?