Unable to allocate enough memory when loading AI file

[Dukwhan Kim]

I tried to open up a .AI file close to 1 MB in size. It shows the PDF import settings and a preview just fine. After I click OK, the dialog box disappears and it resumes loading. Then, after about 30 seconds, an error message pops up:

GLib-ERROR **: gmem.c175: failed to allocate 1073741824 bytes
aborting...

Then it proceeds to a Visual C++ runtime error message, a closing message, and finally the window closes.

I'm running 64-bit Windows Vista on a Quad-Core Intel processor.

[su_v (suv-lp)]

possibly a duplicate of bug #168914. Could you attach an AI file that crashes Inkscape on import?

related recent reports:
Bug #427003 “Fatal error in gc crash on save”
Bug #444940“Too many heap sections

[Dukwhan Kim (ddukki)]

Here's the .ai file I was using.

[su_v (suv-lp)]

reproduced with Inkscape 0.46+devel r22465 on OS X 10.5.8

console messages:
GLib-ERROR **: gmem.c:175: failed to allocate 4294967295 bytes
aborting...

[su_v (suv-lp)]

The file opens without issues in 'Preview.app' (native osx pdf-viewer).

File info:
  PDF version: 1.5
  PDF Producer: Adobe PDF library 9.00
  Content creator: Adobe Illustrator CS3

[ScislaC (scislac)]

With trunk r13454, the offending file opens fine using the Poppler method. If using our standard one, it just hangs here and doesn't seem to take up a ton of ram or end up crashing. In gdb I got tired of waiting and ended up hitting Ctrl+C which threw a segfault related to libcroco and text... given the difference in text handling between poppler and the regular open method it seems worthwhile to at least attach the backtrace for the heck of it.