Comment 26 for bug 132612

I can confirm this bug in Hardy Heron x86_64. A small scanned file quickly uses over 400MB of memory. <strong>Also</strong>, Evince does not free up all the memory when I close the offending document.

Case: (All listed memoryusage is only for the evince-process)
I open two non-scanned mostly text documents and browse through them. Memoryusage: 44 MB.
I open a scanned purely image document, 8 pages 2.5 MB file: Memoryusage before browsing: 257MB.
Memoryusage after browsing through the document: 373MB
Memoryusage after closing the scanned document, keeping the other two up: 177MB
Opening a new scanned document and browse it: 512 MB
Closing this again, still keeping the two text-documents up: 379 MB.

As you can see, the memoryusage escalate as I open and close new documents.