GNOME Bugzilla – Bug 431423
Evince and Evince-thumbnailer allocate ram until the system block
Last modified: 2018-07-17 14:47:53 UTC
with some document opening a file with evince or worst with evince-thumbnailer produce the block of the system because of the ram allocation became too much i provide the link of a document that caused this.. http://www.audiogamma.it/upload/prove_pdf/b&w_802d.pdf the same happen with this gif image (when creating the thumbnail) http://pollycoke.files.wordpress.com/2007/03/plugin1.gif but may be this isn't related
I can confirm this with version 2.22.2 and poppler 0.6.4 (cairo). It usually happens when I open huge PDFs with many images (e.g. scanned images). The whole GNOME Desktop quickly becomes unresponsible. Sometimes I am fast enough to switch to a text-console using CTRL+ALT+F1 for sudo killall -r evince before everything goes down and only magic-syrq works.
well.. now that (finally) someone confirmed this bug could you please take care of it? :) thanks
I guess this bug is already well known. We definitely need to collect more information on the crash so someone can track it down. Vague descriptions that something crashes is definitely not enough for developers. Sadly I do not know how to collect valuable data when the system goes down.
Using an old poppler version like 0.6.4 doesn't help either. I think the problem of the PDFs that contain scanned images will dissapear if you upgrade your poppler.
The PDF file isn't on-line anymore and the GIF image couldn't let me reproduce this bug. Are one of you still experimenting it ?
Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.
Maybe this is the same error: Evince 3.18.2 claims excessive memeoy when opening a multipage file created with AbbyyFineReader14 (AFR14, under Windows). If Evince 3.18.2 (run under Xubuntu 16.04.4, it is the “oficial“ version distributed with Xubuntu 16.04.4 and I found no newer RPM-package for it) loads such a pdf file, after a few seconds, more than 3 GiB of RAM are in use. Then the memory consumption stays almost the stationary for some time to sharply rise again. Finally you may be caught in swapping memory and being almost unable to control the computer. In some cases, after many minutes of heavy CPU use, finally a result is shown. Memory consumption may be up to 6GiB for a two page grayscale pdf document and even for a two page BW-document! In such a case, after stopping Evince, all the memory is back again and the computer is operational as it was before. The same documents load quickly in Firefox 59.0.2 (64-Bit) and without excessive memory consumption. The syndrome does not show up, if Evince shall read a single page pdf document. But even if you add the same content into a single document (in AFR14) to make it a two page document, the result shows the syndrome. The syndrome does not show up with files made by AFR9. GIMP2.8 and LibreOffice (Draw) Build-ID: 1:5.1.6~rc2-0ubuntu1~xenial3 also suffer from the same illness for the same file. Do they all rely on the same libraries? If someone needs sample files to look into it, I can provide some. It even looks like Evince claims this excessive memory already when it is started from a command line and shows the „last opened“ view. I have seen an example when it claimed 3.3GiB and just showed the names of the last opened files with some default icons – maybe it was meant to show a preview of those files in the icons? After waiting some minutes, the icons were filled with previews and then Evince‘s memory consumption dropped down to 48,9 MB!
(In reply to Adalbert.Hanssen from comment #7) > Maybe this is the same error: Evince 3.18.2 claims excessive memeoy when > opening a multipage file created with AbbyyFineReader14 (AFR14, under > Windows). Please, file a new bug report and provide the test case to reproduce the issue.
Germán, yes, it is. Since the Evince team did not react on my posting, I postetd another bug report after I found out that all programs which depend on the poppler library suffer the same sickness for the same files generated by AFR14: https://bugs.freedesktop.org/show_bug.cgi?id=106781 I tested many cases and I found that most of the files, which suffer the >1 pages syndrome and which were produced by AFR14, still conform to PDFA-2FA-1B. Despite that, they had the excessive memory and CPU usage syndrome. I encountered no case of a searchable file from AFR14 with more than one page which smoothly opens in any poppler based program. Kind regards Adalbert Hanßen
According to the people from Abbyy Fine Reader the error is caused by a "linearisation problem" in AFR14 and it will be fixed there. However for files which show the syndrome I found out that they comply to the norm according to VeraPdf. According to the people of Abbyy Fine Reader, the error does no longer show up for Poppler Version > 0.50. However I was unable to check this with Evince since I have no version of Evince at hand which incorporates a version of Poppler>0.50. I only found that pdftotext version 0.66.0 did not use excessive memory nor excessive usage of CPU. Unfortunately I can not switch back to version 0.41.0 which belongs to Xubuntu 16.04.4. It would be helpful if one could lift all Poppler-dependant programs to a version > 0.50 without changing the version of the operating system.
(In reply to Adalbert.Hanssen from comment #10) > It would be helpful if one could lift all Poppler-dependant programs to a > version > 0.50 without changing the version of the operating system. You could try installing evince from flatpak or snap since those are more self-contained. But also you should know that evince doesn't use this bug tracker any more so it's likely no one will look at any issues you post here. It has moved to https://gitlab.gnome.org/GNOME/evince. Also, this isn't really an appropriate place to post about this, since this was an issue in poppler, not evince, and it appears it was fixed some time ago.