Comment 15 for bug 952108

More Infos:
I'm also on Precise and confirm this bug it's really annoying a lot!

In my case Nautilus regularly eats memory while simply copying files.
I've started to copy a large tree of small files two days ago in the morning from an USB disk to another; the copy was the only process in a regular running state. I came back home yesterday, 36 hours later, and nautilus copy was still running using about 1/3 of my 8GB of precious RAM while copying at only 1MB/sec against usual 10-15MB/sec; CPU usage was also very high, near 100% of the used processor.
I stopped the process, rebooted and started to copy a smaller tree each time.
The memory leak was always in place for each tree I copied, increasing the memory used as well as the charge on the CPU taking care of running the process; these are collected steps:
- 1st tree (13.3GB,55k files): RAM 0.76%->1.94%(+1.18%), ~12MB/sec, ~5-6%CPU
- 2nd tree (8,5GB,30k files): RAM 1.95%->2.39%(+0.44%), ~10MB/sec, ~8-10% CPU
- 3rd tree (14,0GB,50k files): RAM 2.40%->3.52%(+1.12%), ~9MB/sec, ~11-15%CPU
- 4th tree (13,6GB,48k files): RAM 3.53%->4.55%(+1.02%), ~8MB/sec, ~14-20%CPU
- 5th tree (20,9GB,105k files): RAM 4.56%->6.69%(+2.13%), ~7MB/sec, ~17-25%CPU
- 6th tree (28,8GB,146k files): RAM 6,70%->9,86%(+2.16%), ~6MB/sec, ~20-30%CPU
The memory leak seems loosely coupled to the number of copied files, maybe to the total length of the filenames managed?
The higher CPU usage seems simply related to the waste of RAM memory.
When the copy was completed nautilus CPU usage went down to 0.17% while RAM usage remained 9.86%.

It could be interesting I'm using:
- Dropbox
- Desktop Background Image changing (Webilder)
but changing in RAM/CPU usage did not seem at all related to these processes.