I had the same problem on Ubuntu 12.04.2 LTS 64bits. I left my computer running during the week-end (with 4 programs running with < 100Mio usage each) and I ended up with nautilus eating 3 Gio RAM. It was the limit of my RAM and I was lucky enough to have enough responsiveness when I came back to identify and kill nautilus.
This is a critical bug since it can render a computer non-responsive if nautilus is not killed in time, however as it seems to be increasing over a long period of time, it is difficult to pinpoint what is wrong. The fact that this bug don't seem to be widespread also suggest that either the flavor of Ubuntu used is rare (12.04 64 ?), or that some special events must occur for this bug to manifest itself.
Notes :
- I don't remember having any nautilus opened
- I don't have big pictures that would need a lot of thumbnail
- I use nautilus-terminal
I had the same problem on Ubuntu 12.04.2 LTS 64bits. I left my computer running during the week-end (with 4 programs running with < 100Mio usage each) and I ended up with nautilus eating 3 Gio RAM. It was the limit of my RAM and I was lucky enough to have enough responsiveness when I came back to identify and kill nautilus.
This is a critical bug since it can render a computer non-responsive if nautilus is not killed in time, however as it seems to be increasing over a long period of time, it is difficult to pinpoint what is wrong. The fact that this bug don't seem to be widespread also suggest that either the flavor of Ubuntu used is rare (12.04 64 ?), or that some special events must occur for this bug to manifest itself.
Notes :
- I don't remember having any nautilus opened
- I don't have big pictures that would need a lot of thumbnail
- I use nautilus-terminal