> Nautilus eats 99% CPU when I start browsing through certain folders
are those “certain folders” on the same hard drive and petition that
the system files are on? or,
different petition? or,
different hard drive? or,
connected via USB, or,
different machine? or,
distant network? or,
network data having too many collisions? or,
different operating system? or,
and, what is the file system in use on those certain folders?
is the partition of those folders horribly fragmented?
is the drive is healthy?
and, what is in those “certain folders”? that is, if it is full of
(say) photos that have to be read and rendered as a graphic…then,
that is gonna take some heavy computation power…make the graphics
smaller or turn off preview in those folders…
my point is the slowness and problem might have little or nothing to
do with Nautilus itself but instead where the folders are and what is
hmmmmmmmmmmmmmm…i give up…well, just for fun you might try using
YaST (or zypper) and update Nautilus…maybe some little bit of code
got scrambled somewhere…otherwise, i have no idea…so, i turn you
over to the real guru . . .
hmmmm…are these folders in your /home? maybe try adding a new user,
give that new user permission to browse that/those directories and see
if the problem persists…
I took your suggestion: logged in as root under Gnome I have no problems browsing through the folders.
Under the account itself I can browse without problems through it with konqueror.
All in all very weird, there are no hidden files etc in the folder, no special things. I tried to attach gdb to the crashing nautilus, but in some weird way gdb doesn’t react anymore to ctrl c after nautilus gets killed by gnome itself (i.e. I cannot print the stack stuff etc).