I'm also seeing this bug on Precise 64-bit, but for me Nautilus grows to eat several GiB of RAM (that's "RSS", sometimes up to 8 GiB of "VIRT") before I (have to) kill it...
Just like the original reporter, some Nautilus windows/tabs might show directories with a lot (thousands) of files and/or subdirectories in them, sometimes with the subdirectories opened so that their contents are also visible (sometimes several levels deep), and there can be changes (either as a result of actions in other Nautilus windows/tabs, or by other programs) that Nautilus has to update its view for. I suppose that lots of directory entries and/or frequent updates would make the impact of memory leaks in certain code paths more visible...
I usually have about 2-5 Nautilus windows and maybe a total of 10 tabs in them open, but I don't often open/close new tabs or windows.
I also tried this with a system that had no custom nautilus extensions (so only what is installed by default, plus even some of those uninstalled), but that didn't solve the problem.
I'm also seeing this bug on Precise 64-bit, but for me Nautilus grows to eat several GiB of RAM (that's "RSS", sometimes up to 8 GiB of "VIRT") before I (have to) kill it...
Just like the original reporter, some Nautilus windows/tabs might show directories with a lot (thousands) of files and/or subdirectories in them, sometimes with the subdirectories opened so that their contents are also visible (sometimes several levels deep), and there can be changes (either as a result of actions in other Nautilus windows/tabs, or by other programs) that Nautilus has to update its view for. I suppose that lots of directory entries and/or frequent updates would make the impact of memory leaks in certain code paths more visible...
I usually have about 2-5 Nautilus windows and maybe a total of 10 tabs in them open, but I don't often open/close new tabs or windows.
I also tried this with a system that had no custom nautilus extensions (so only what is installed by default, plus even some of those uninstalled), but that didn't solve the problem.