Unable to allocate enough memory when loading large PDF file

Bug #846389 reported by HelloTheWorld on 2011-09-10
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

When i'am uploading a (quite big) PDF file, it's starting, and **like shown in the image attachement**, it's loading memory until crash.

I attached a ZIP, with :
a) image of System Memory Load Oversized
b) PDF file crashing.

GLib-Error **: gmem.c:202: failed to allocate 12582912 bytes
[end of message]


This application has requested the Runtime to terminate it in an unusual way.
Please contact the support team for more information.
[end of message]


GLib-Error **: gmem.c:202: failed to allocate 12582912 bytes

GLib-GObject-Warning (recused) **:gsignal.c:2275: signal 'composited changed' is invalid for instance '02CEC070'
[end of message]

then again : " This application has requested the Runtime to terminate..."

The PDF file attached is a PDF file from an COPYRIGHTED image. It is provided as a DEBUG SUPPORT ATTACHMENT only, and MUST NOT be used in an other way, for any other application. Using this image for other use would exposes you to legal proceedings.

HelloTheWorld (loic-dupont) wrote :

System :
Windows 7, SP1, 32bits

Mem :
4,00 Go (3.25 Go used)

Inkscape :
Inkscape 0.48.2 r9819

su_v (suv-lp) on 2011-09-10
tags: added: importing pdf performance
removed: 202 2275 glib gmem.c gsignal.c memory
su_v (suv-lp) wrote :

The attached sample PDF file nearly brought down my whole system [1] due to enormous memory consumption when trying to simply preview using the system's native PDF viewing capabilites (Mac OS X does have native support for PDF). I won't even try to open it in Inkscape and leave testing it to others.

Can you provide some information about which application was used to create the PDF file, and whether other PDF viewers (let alone PDF editors) handle it on your system without exhausting all available memory?

[1] Mac OS X 10.5.8 (i386), 2GB RAM, 2.4 GHz Intel Core 2 Duo)

Changed in inkscape:
importance: Undecided → High
su_v (suv-lp) wrote :

> (…) information about which application was used to create the PDF file

Nevermind - Evince 2.30.3 did handle the file better (took about 2 minutes of processing time to load and render it) and provided me the requested information:
The file was created with Neevia docuPrinter Pro v6.2 (Trial) (converting 'fig1.eps' to PDF-1.4).

There have been earlier reports about PDF files created by Neevia and failing to open in Inskcape on Windows, see for example the discussion in Bug #427003 “Fatal error in gc crash on save” <https://bugs.launchpad.net/inkscape/+bug/427003> which produced better results importing the original EPS file in Inkscape IIRC.

tags: added: crash
su_v (suv-lp) wrote :

I tried to open the PDF in Inkscape 0.48.2 and 0.48+devel r10627 (using the experimental 'Adobe PDF via cairo-poppler' file format) on Mac OS X 10.5.8 (i386) and both tries ended with Inkscape exhausting all available memory (extensive swapping involved) and crashing ("Emergency save activated!") with the same glib error in gmem.c (after several minutes of CPU time).

This type of error has been reported several times already (for importing large PDF files or PDF files with a certain type of content/structure). Anyone volunteering for searching and listing earlier reports?

Changed in inkscape:
status: New → Confirmed
su_v (suv-lp) wrote :

Incomplete list of earlier reports about the same or related issue:

bug #717906 Glib-ERROR **: gmem.c:136: failed to allocate 6144 bytes Aborting…
bug #450898 Win64: AI import fails trying to allocate 1 GB of memory
bug #392421 Crash when open *.ai more tham 500mb
bug #367779 Out of memory crash while importing large pdf

HelloTheWorld (loic-dupont) wrote :

Hi !

Sorry for the delay... Too busy is not an excuse, but an explanation. :)

This PDF file hase been created by the user of a Photoshop or Draw (or whatever) user, and I bought the file (legally !!!!) on a image site.
I can't tell you much more...

jazzynico (jazzynico) on 2016-06-10
summary: - uploading (big) PDF file load *physical* memory until crash
+ Unable to allocate enough memory when loading large PDF file
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers