Export to PNG crashes at dpi > 150 [0.48.2 - Win7]

[Simone Bianchini]

Hello everyone and thanks in advance for your help.

I'm trying to export to PNG (at high dpi, I was actually aiming for 300) a huge composition with many objects comprised of thousands of nodes, the problem is that Inkscape just crashes everytime I prompt the exporting process.

I'm using Inkscape 0.48.2, Windows 7, 8 Gb of RAM an i5 2500k microprocessor and a 560 Ti graphic card.

I will attach the file that's causing me troubles as well (I just hope that you guys will be able to open it correctly without the gradients filters files, just let me know if it won't work).

[Simone Bianchini (retristicks)]

by the way, the gradients should look like this (although the image in the linked file is slightly different):

[img]http://img11.imageshack.us/img11/8069/ccthumbnailr.jpg[/img]

[su_v (suv-lp)]

> (I just hope that you guys will be able to open it
> correctly without the gradients filters files, just
> let me know if it won't work).

Could you please explain what "gradient filter files" would be? Note: the filter definitions of applied filter effects are stored within each SVG file, even if you applied them from custom predefined effects (e.g. made available in menu 'Filters > Personal', or copy&pasted from another file).

AFAICT based on the naming of the custom filter effects and the looks of the drawing, it makes use of the sample filter effects provided by Ivan Louette in this InkscapeForum topic:
<http://www.inkscapeforum.com/viewtopic.php?f=5&t=9612>

[su_v (suv-lp)]

On OS X 10.7.4 (64bit) with Inkscape 0.48.3.1 and 0.48.x r1990:
- crash not reproduced at 150 dpi and 200 dpi
- crash reproduced at 240 and 300 dpi with these console messages:

** (inkscape:68358): WARNING **: 100694000 bytes requested for pixel buffer, I won't try to allocate that.

** (inkscape:68358): WARNING **: Memory allocation failed in Inkscape::Filters::FilterSlot::set (transform)

(Possibly related to bug #613731 (?)).

[su_v (suv-lp)]

Correction (typo):
- On OS X 10.7.4 (64bit) with Inkscape 0.48.3.1 and 0.48.x r1990:
+ On OS X 10.7.4 (64bit) with Inkscape 0.48.3.1 and 0.48.x r9900:

[su_v (suv-lp)]

Crash not reproduced at 300 dpi with current trunk (Inkscape 0.48+devel r11443) on OS X 10.7.4 (64bit)
Hardware: MBP 13", 8 GB RAM, 2.4 GHz Intel Core i5

Without multi-threading enabled, the export at this resolution (9439 x 8122 pixels (300 dpi)) took ~132m.

Command line used for export:
$ inkscape -D -e yellowbackfinal5-r11443-300dpi.png -d 300 -f yellowbackfinal5.svg

[su_v (suv-lp)]

> Crash not reproduced at 300 dpi with current trunk (…) on OS X

@Alvin or @JazzyNico - could one of you confirm this with a recent development build on Windows?

[Alvin Penner (apenner)]

crash confirmed on Windows 7, Inkscape 0.48.3
- at 90 dpi I get the below warnings, but also got a .png file size = 836K
- at 300 dpi I get an immediate crash with the memory allocation error below.

C:\Program Files\Inkscape>inkscape

** (inkscape.exe:2852): WARNING **: Unable to open linked file: C:\Documents and
 Settings\Primo\Desktop\4chan meme's\Rossy\Challenge Court Reference\PATCH100dpi
.png

** (inkscape.exe:2852): WARNING **: Unable to open linked file: C:\Documents and Settings\Primo\Desktop\4chan meme's\Rossy\Challenge Court Reference\Tshirt\polo
mockupbitmap.PNG

** (inkscape.exe:2852): WARNING **: Unable to open linked file: C:\Documents and Settings\Primo\Desktop\4chan meme's\Rossy\Challenge Court Reference\PATCH100dpi
.png

** (inkscape.exe:2852): WARNING **: Unable to open linked file: C:\Documents and Settings\Primo\Desktop\4chan meme's\Rossy\Challenge Court Reference\Tshirt\polo
mockupbitmap.PNG

** (inkscape.exe:2852): WARNING **: 156613344 bytes requested for pixel buffer,I won't try to allocate that.

** (inkscape.exe:2852): WARNING **: Memory allocation failed in Inkscape::Filters::FilterSlot::set (transform)

[su_v (suv-lp)]

<off-topic>
The original SVG file has a huge amount of unused resources (mostly gradients) in the <defs> section (use 'File > Vacuum defs' to clean them up), and two hidden parts (resulting from hidden layers of imported drawings which are not visible).

After cleaning up the file (defs, deleting the stuff which is hidden anyway (with help of 'Edit > XML Editor')), the file size is reduced to 211'841 Bytes (from 2'134'770 Bytes), which does lower the initial memory footprint of the file at least a bit.
</off-topic>

[su_v (suv-lp)]

> New → Confirmed

@Alvin - I could already have confirmed the crash with stable Inkscape (see comment #4): the real question is whether current trunk with the new renderer and the updated devlibs still immediately crashes on Windows when trying to export at a higher resolution (300 dpi), or whether the report can be set to status 'Fix Committed'.

[su_v (suv-lp)]

<off-topic>
@Alvin - please accept my apologies for my impolite and impatient last comment - I'm aware that it does takes quite a while to export at such sizes, and success can only be confirmed at the end because Inkscape might fail at any point during that lengthy process.
</off-topic>

[Alvin Penner (apenner)]

on Windows XP, Inkscape rev 11367, at 300 dpi, I get a crash after about 10 minutes or so, with the messages

** (inkscape.exe:2796): WARNING **: Unable to open linked file: C:\Documents and Settings\Primo\Desktop\4chan meme's\Rossy\Challenge Court Reference\PATCH100dpi
.png

** (inkscape.exe:2796): WARNING **: Unable to open linked file: C:\Documents and Settings\Primo\Desktop\4chan meme's\Rossy\Challenge Court Reference\Tshirt\polo
mockupbitmap.PNG

(inkscape.exe:2796): Gtk-CRITICAL **: gtk_window_set_transient_for: assertion `parent == NULL || GTK_IS_WINDOW (parent)' failed

(inkscape.exe:2796): GLib-GObject-WARNING **: invalid cast from `(null)' to `GtkWidget'

(inkscape.exe:2796): Gtk-CRITICAL **: gtk_widget_get_window: assertion `GTK_IS_WIDGET (widget)' failed

(inkscape.exe:2796): Gdk-WARNING **: gdkdrawable-win32.c:2013 drawable is not a pixmap or window

Emergency save activated!
Emergency save completed. Inkscape will close now.

[jazzynico (jazzynico)]

Crash reproduced on Windows XP, Inkscape trunk revision 11859.
Inkscape eats all available memory and then exits.