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 512438 - Eats up all virtual memory on specific file
Eats up all virtual memory on specific file
Status: RESOLVED DUPLICATE of bug 504913
Product: evince
Classification: Core
Component: PDF
2.20.x
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
: 517566 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-01-27 19:50 UTC by Sven Arvidsson
Modified: 2009-04-28 13:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sven Arvidsson 2008-01-27 19:50:07 UTC 
[ From http://bugs.debian.org/461788 by Stanislav Maslovski ]

"Download this pdf: http://vt100.net/tektronix/4014-um/4014-um.pdf and open it with evince. Try to navigate in the document (pressing PageDown for ex.), you will notice how fast memory gets consumed. Soon evince will eat up all available virtual memory and will be killed by the kernel.

This is vmstat output (almost) at the moment when evince gets killed by the kernel:
(This machine has 512 Mb RAM and ~720 Mb of swap)

$ vmstat
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa
 2  4 707552   5072    624  13888   10   93   161   125  485  740  5  1 92  2"
Comment 1 Carlos Garcia Campos 2008-02-08 11:28:21 UTC 
I can't reproduce it.
Comment 2 Sven Arvidsson 2008-02-10 18:43:42 UTC 
For me, memory usage is unusually high, but jumps around when I scroll around in the document. 

It doesn't simply start eating away at the memory, but instead jumps between using something like 20%, 60%, 40% (of my 1GB of RAM) and only occasionally go higher and starts swapping.

I'm using evince 2.20.2, poppler 0.6.2 and cairo 1.4.14.
Comment 3 Carlos Garcia Campos 2008-02-20 08:43:58 UTC 
*** Bug 517566 has been marked as a duplicate of this bug. ***
Comment 4 Alexander Kojevnikov 2009-04-28 13:57:36 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 ***