Crash on PNG bitmap export

Bug #1256699 reported by Frank Niemann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Fix Committed
High
Unassigned

Bug Description

Inkscape 0.48.2 and 0.48.4 under Windows 7:
I have a rather large drawing - 7.4 MB, 4 visible layers plus various linked bitmaps (imported background maps, hidden). Whenever I try to export a bitmap, Inkscape crashes after having produced between 25% and 50% of the bitmap. I have already tried various workarounds (fitting the page size to the drawing, masking parts outside the intended print range, varying the export resolution) to no avail. A print to PDF does also not work correctly - some layers are not printed at all or incorrectly.
Opening the .svg with windows explorer, and saving as picture from there, however, works without problems (though not allowing for any resizing, which then again has to be done via bitmap import into incscape).

The drawing creating the problems is attached.

Revision history for this message
Frank Niemann (3-info-p) wrote :
jazzynico (jazzynico)
tags: added: bitmap crash exporting
Changed in inkscape:
importance: Undecided → High
Revision history for this message
jazzynico (jazzynico) wrote :

Not reproduced on Crunchbang Waldorf (a Debian stable based distro), with Inkscape 0.48.3.1 and trunk revision 12833.

Exported PNG attached.

Revision history for this message
su_v (suv-lp) wrote :

Crash not reproduced with the provided file (see attached image: it exports rather quickly with Inkscape 0.48.4 on OS X 10.7.5, with default export settings: export page area, at 90dpi).

> (…) 7.4 MB, 4 visible layers plus various linked bitmaps (…)

Linked bitmap images are not included in the rar file -> it is not possible to test same export conditions on other systems. There is also no information given about export options used (bitmap size, dpi).

Revision history for this message
jazzynico (jazzynico) wrote :

Confirmed on Windows XP, Inkscape 0.48.4. With a 2 Gio RAM configuration, exporting fails and crashes the application with memory errors. With only 1 Gio RAM, the file doesn't even load.

Fixed in the trunk.

Changed in inkscape:
milestone: none → 0.49
status: New → Fix Committed
tags: added: win32
Revision history for this message
jazzynico (jazzynico) wrote :

Marking duplicate of Bug #631908 "inkscape version 0.48 crash with runtime error on loading svg and on export".

Revision history for this message
Frank Niemann (3-info-p) wrote :

Exported png in comment #2 includes errors:
Layer "Gemeinden" - Group "Gemeinden WL" - path id "Undeloh-Wesel" is coloured dark gray, but displayed in white on the export bitmap.
Yellow artefact on the bottom of the picture (southernmost communities, a bit east of the centre) stretching in horizontally from the yellow border eastwards into the two adjacent paths (communities).

Same bug, or a new one?

Revision history for this message
su_v (suv-lp) wrote :

> coloured dark gray, but displayed in white

Known issue with old renderer in current stable version, fixed with new cairo-based renderer in current trunk (see attached bitmap export with r12833).

> Yellow artefact on the bottom of the picture

Sorry, failed to spot this error in the image exported with current stable…

Revision history for this message
Frank Niemann (3-info-p) wrote :

While you and I are at it- another bug in the file:
Layer "Gewässer" Group "Flüsse" Path "Norderelbe" stops displaying on screen and export (including your latest attachment) when a clip path is being set on it. Once the clip path has been set, it also can't be removed with the Object->clip path->remove command. When I remove the clip path manually via the XML editor, or via "undo last command" (that one works), the object displays again.

The effect takes both place when the clip path is in a different layer (as originally), and when I create a clip path in the same layer.

Revision history for this message
su_v (suv-lp) wrote :

<off-topic>
> While you and I are at it- another bug in the file:

Please note that your questions which do not relate to the original report (crash on bitmap export on Windows) are also sent to the subscribers of the report this was marked as duplicate off. I recommend to use different venues for questions ('Answers' section, mailing list, or a new report if you suspect a (different, unrelated!) bug than using the comments section of a bug report which has been triaged and linked as duplicates to an existing report.
</off-topic>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.