After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 469235 - evince is a memory hog
evince is a memory hog
Status: RESOLVED DUPLICATE of bug 504913
Product: evince
Classification: Core
Component: PDF
0.9.x
Other All
: Normal critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-22 13:01 UTC by Pierre Ossman
Modified: 2009-04-28 14:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Attachments
valgrind.log (28.33 KB, text/plain)
2007-08-22 14:42 UTC, Pierre Ossman
Details
Memory map of evince (303.43 KB, image/jpeg)
2008-10-12 13:36 UTC, Maneesh Upmanyu
Details

Description Pierre Ossman 2007-08-22 13:01:52 UTC
Please describe the problem:
Recent versions of evince eats memory like crazy. Opening any document quickly eats over 100 MB, and opening a large document (at least tens of pages) makes the system slow to a crawl.

Example:

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND            
16211 drzeus    20   0  417m 264m 6276 S  0.0 52.5   0:09.56 evince  

Perhaps the system requirement should specify "At least 2GB RAM" ;)


Steps to reproduce:
Open any document, the larger the better.

Actual results:
Machines swaps like there's no tomorrow.

Expected results:
Reasonable memory usage.

Does this happen every time?
Yes.

Other information:
Comment 1 Carlos Garcia Campos 2007-08-22 13:44:02 UTC
I can't reproduce it. Could you attach a valgrind log file here, please?

Thanks for reporting. 
Comment 2 Pierre Ossman 2007-08-22 14:42:57 UTC
Created attachment 94122 [details]
valgrind.log

Attached, although it seems to be missing things. The number it claims is nowhere near what top states.
Comment 3 André Klapper 2008-06-08 12:11:31 UTC
reopening.
Comment 4 badpazzword+gnome 2008-07-24 12:04:51 UTC
http://elettrotecnica.albertomiorin.com/appunti.html

Pretty much all of the (huge) PDFs in that webpage bring Evince's memory usage over the top, down into the OOM killer. Time is a factor. Going up and down the documents leads in overlong "Loading..." times.

Example:

http://elettrotecnica.albertomiorin.com/Appunti/Capitolo5-senza%20pag%20162.pdf (31 pages in 21.4 MB) (!)

From kern.log:

> Jul 24 13:31:18 bPortatile kernel: [13971.379398] evince invoked oom-killer: gfp_mask=0x1201d2, order=0, oomkilladj=0
> Jul 24 13:31:18 bPortatile kernel: [13971.379412] Pid: 15154, comm: evince Not tainted 2.6.24-20-generic #1
> <snip>
> Jul 24 13:31:18 bPortatile kernel: [13971.389826] Out of memory: kill process 15154 (evince) score 129949 or a child
> Jul 24 13:31:18 bPortatile kernel: [13971.389870] Killed process 15154 (evince)

From htop: (I reopened evince a few seconds after the OOM freeze.)

> Load average: 0.19 0.33 0.50            Uptime: 06:43:48
> Tasks: 247 total, 1 running             Time: 13:59:15
>   PID USER     PRI  NI  VIRT   RES   SHR S CPU% MEM%   TIME+  Command
> <snip>
> 23438 badp      20   0  147M  116M 13148 S  0.0 11.6  0:19.92 evince
> 23437 badp      20   0  147M  116M 13148 S  0.0 11.6  0:21.67 evince

My swap is disabled; I have 1002 MB of dedicated RAM.
Comment 5 Nickolay V. Shmyrev 2008-07-25 07:16:03 UTC
This document works perfectly here. I think you just need to update poppler.

3290 shmyrev   20   0 83344  44m  12m S    0  2.2   0:15.73 evince 
Comment 6 Maneesh Upmanyu 2008-10-12 13:36:59 UTC
Created attachment 120437 [details]
Memory map of evince

Memory map for evince. opening a 2mb pdf consumes more than 450mb of memory. Same pdf takes 15mb for kpdf.
Comment 7 Maneesh Upmanyu 2008-10-12 13:40:11 UTC
As soon as I open a pdf, evice hogs up as much as ~450mb of memory. 

3820 Upmanyu   20   0  487m 415m  10m S    0 41.5   0:06.02 evince      
 
am using: kernel: 2.6.23.1-42.fc8
evince: evince-2.20.2-1.fc8
poppler: poppler-0.6-2.fc8
       
attachment: memory map of the process

the same pdf when opened with kpdf takes ~15mb of memory
Comment 8 Alexander Kojevnikov 2009-04-28 14:12:52 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 504913 ***