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 516067 - memory eating
memory eating
Status: RESOLVED DUPLICATE of bug 504913
Product: evince
Classification: Core
Component: PDF
2.20.x
Other All
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
: 522684 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-02-12 18:12 UTC by j.silvestre
Modified: 2008-05-06 05:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description j.silvestre 2008-02-12 18:12:18 UTC 
Please describe the problem:
evince eats all the available memory when viewing some pdf files. 
Evince gives back the memory when closed.

Steps to reproduce:
1. open this file: http://www.farnell.com/datasheets/57316.pdf
2. or that one : http://www.tycoelectronics.com/industry/appliance/pdf/catalogs/1309245_PEseries.pdf
3. 


Actual results:
evince burn cpu and then eats all the memory

Expected results:
behave normally!

Does this happen every time?
yes with the given files. Found an another one pdf file but lost the url...

Other information:
Comment 1 Carlos Garcia Campos 2008-02-16 10:43:25 UTC 
I can't reproduce it. What poppler version do you have installed? What backend? (You can check this in Evince Help -> About). Thanks.
Comment 2 j.silvestre 2008-02-16 10:55:12 UTC 
Evince says : poppler 0.6 (cairo)

If it can help xpdf have no problems with those pdf.

All the best.
Comment 3 Pavel Šefránek 2008-04-06 15:09:18 UTC 
*** Bug 522684 has been marked as a duplicate of this bug. ***
Comment 4 Alexander Kojevnikov 2008-05-06 04:45:35 UTC 
I think this bug report is a duplicate of bug 504913, which presumably was
fixed in the trunk.
Comment 5 Akhil Laddha 2008-05-06 05:01:27 UTC 
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you
find.

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