Bug 60901 - High memory consumption (which leads to OS freeze) on previewing/opening of attached pdf file
Summary: High memory consumption (which leads to OS freeze) on previewing/opening of a...
Status: RESOLVED DUPLICATE of bug 33364
Alias: None
Product: poppler
Classification: Unclassified
Component: cairo backend (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-15 15:08 UTC by cpacchierotti
Modified: 2014-11-01 05:40 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
pdf file which make Evince request all the memory (6.78 KB, application/pdf)
2013-02-15 15:08 UTC, cpacchierotti 		Details
View All

Description cpacchierotti 2013-02-15 15:08:32 UTC 
Created attachment 74873 [details]
pdf file which make Evince request all the memory

Every time I try to open or even just preview on Nautilus the pdf file
attached, Evince starts demanding all the memory. This leads to a complete freeze of the OS if you don't have enough memory (it requests ~4G of RAM).

On Evince's bigzilla (https://bugzilla.gnome.org/show_bug.cgi?id=693869) this was recognized to be poppler's problem and it was affecting multiple users.

Info:
poppler-0.20.2-9.fc18.x86_64

Linux localhost.localdomain 3.7.6-201.fc18.x86_64 #1 SMP Mon Feb 4 15:54:08 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux

Fedora 18



Thank you,
Comment 1 Jose Aliste 2013-02-15 15:13:21 UTC 
seems to be  a cairo backend bug. In my machine, with poppler-glib-demo uses more than 4GB to render the file. pdftoppm is almost instant without high memory consupmtion. pdftocairo also uses a lot of memory (but seems less than poppler-glib-demo)
Comment 2 Adrian Johnson 2014-11-01 05:40:45 UTC 
pdftocairo uses 6GB of memory to render the pdf. After applying the patch in bug 33364 it uses 16MB.

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

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.