Comment 11 for bug 132612

I can also confirm this bug on Gutsy.

As with others here, on Feisty Evince was reasonable, but on Gutsy things are out of control. I simply cannot use Evince (I am using xpdf for now). One example is a 2.6MB PDF (I can post it here if it can help), that when opened in Evince causes 300+ MB of resident memory to be used (and I can actually see the memory taken up and swap space being utilized - this isn't a misreading of memory usage due to caching/buffers). After initial load, memory usage goes down to 200 MB, but jumps back up to 300MB+ (and 100% CPU) as I scroll.

On my 512 MB system, this behavior basically sends everything else into swap, and the system is nearly unusable. Note that even the 200MB that it 'stabilizes' on when not scrolling is bad enough.