Bug 54684 - Nautilus fills all RAM in some cases
Nautilus fills all RAM in some cases
Product: Red Hat Linux
Classification: Retired
Component: gnome-vfs (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Havoc Pennington
Aaron Brown
Depends On:
  Show dependency treegraph
Reported: 2001-10-16 05:52 EDT by Alan Cox
Modified: 2007-04-18 12:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-10-22 16:47:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alan Cox 2001-10-16 05:52:49 EDT
Nautilus on a Cyrix MediaGX.

Originally I thought Nautilus was just using too much memory but when I
compared to another box this was obviously not the problem. In fact I was
seeing nautilus expand to fill ram then die

Removing a symlink to itself in my home dir (the dir I was opening a window
view of) fixed the problem

I had

xxx symlinked to xxx

Comment 1 Havoc Pennington 2001-10-16 10:43:33 EDT
You put that xxx->xxx link there just to break things didn't you. ;-) 

No doubt a pretty easy bug to fix, just slap a limit on symlink-chasing.
Comment 2 Havoc Pennington 2001-10-16 23:55:31 EDT
Upstream as http://bugzilla.gnome.org/show_bug.cgi?id=62494, 
for reference.
Comment 3 Havoc Pennington 2001-10-19 12:29:52 EDT
Putting an foo->foo link in a random directory did not cause this problem. 
It must be triggered if the link is in your home dir, or maybe if a dir gets
lots of change notifications, or the like...
Comment 4 Anders Carlsson 2001-10-19 12:33:30 EDT
I also don't get it when putting a link in a random directory. Making it on the
desktop triggers it though.
Comment 5 Havoc Pennington 2001-10-22 16:47:40 EDT
I think I found the problem in gnome-vfs, fix in the works.
Comment 6 Havoc Pennington 2001-10-23 14:56:13 EDT
gnome-vfs 1.0.1-18 resolves the problem for me.

Note You need to log in before you can comment on or make changes to this bug.