Comment 6 for bug 132612

I am also experiencing a very bad regression in gutsy with respect to memory usage in evince. Evince has always used a lot of memory, but it seems much, much worse in Gutsy. For example, this document: http://www.stanford.edu/class/cs242/readings/backus.pdf causes evince to use hundreds of megabytes of memory. While I'm reading the document, the memory usage keeps going up until I run out of memory and start swapping. With this particular document I can go from a freshly booted system with no other applications running (< 200 MB of RAM) to a state where the system is swapping within a few minutes (I have 512 MB of RAM).

I'm using the intel video card driver (the modesetting one called "intel", not "i810"), so it seems unlikely that this is a video card issue given that I and the original bug reporter have two totally different video cards.

Is there some option in the deb that has been turned on since Feisty that could cause this (e.g. I know cairo support has been enabled/disabled many times)? Is there anything I can do to get the old memory profile from evince?