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 605083 - evince uses too much memory
evince uses too much memory
Status: RESOLVED OBSOLETE
Product: evince
Classification: Core
Component: general
2.28.x
Other Windows
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
: 605692 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-12-20 18:39 UTC by Jack Tanner
Modified: 2018-05-22 13:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jack Tanner 2009-12-20 18:39:25 UTC
I know that measuring memory usage is a whole science onto itself, but it seems that Evince uses far too much RAM.

On Windows 7 (32 bit), Evince 2.28.0 needs more than 50MB RAM to load this file, while Acrobat Reader 9.2 uses about 20 MB RAM. Numbers are "Private Working Set".

http://www.rawtherapee.com/data/RawTherapeeManual_2.4.pdf

I have another file, not public, unfortunately. On disk, it's a 17MB PDF of a 200 page book. Evince uses over a gig of RAM.
Comment 1 Fabio Durán Verdugo 2009-12-20 22:31:32 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.
Comment 2 Jack Tanner 2009-12-21 04:56:17 UTC
Fabio, I grant that my bug report could be more detailed, but I don't know what specific additional information is necessary. The bug-HOWTO is far too generic. Perhaps an Evince developer could chime in?
Comment 3 Carlos Garcia Campos 2009-12-21 10:57:14 UTC
Well, Evince uses more memory than acroread, but that's not necessarily a bug, because evince is also much faster than acroread (at least in Unix). Evince caches more pages into memory than acroread, which requires more memory but makes it faster too. 

So, 50MB doesn't look like a bug to me, but 1Gb it's definitely an issue. Without the document there's not much we can do, though. 

Thanks for reporting.
Comment 4 Jack Tanner 2009-12-21 16:00:36 UTC
Carlos, thanks for the explanation. I'll find a public PDF that shows ridiculous memory behavior and post that here. If there's a new 2.28.x build for Windows, I can test with that. If not, I'll test with 2.28.0.
Comment 5 Jack Tanner 2009-12-21 20:46:31 UTC
I've narrowed down the bug a bit. There are some PDFs that Evince loads with good memory usage (say, 20 MB private working set), but when searching through those PDFs (Ctrl+F), private working set grows dramatically (by tens or hundreds of megabytes). I can reproduce this on three different files, but none are publicly available and I can't attach them here. However, I'm happy to email the PDF to a developer directly. Any takers?
Comment 6 André Klapper 2010-01-02 19:53:11 UTC
*** Bug 605692 has been marked as a duplicate of this bug. ***
Comment 7 Germán Poo-Caamaño 2013-11-02 08:09:04 UTC
(In reply to comment #5)
> I've narrowed down the bug a bit. There are some PDFs that Evince loads with
> good memory usage (say, 20 MB private working set), but when searching through
> those PDFs (Ctrl+F), private working set grows dramatically (by tens or
> hundreds of megabytes). I can reproduce this on three different files, but none
> are publicly available and I can't attach them here. However, I'm happy to
> email the PDF to a developer directly. Any takers?

Do you still can reproduce the issue with a newer Evince?

If any of those document are behind a paywall, can you point us the links?
Comment 8 GNOME Infrastructure Team 2018-05-22 13:43:11 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/evince/issues/122.