stroked and scaled Linked Offset text causes a crash upon open file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Fix Released
|
High
|
Unassigned |
Bug Description
I Love Inkscape - I didn't know I could be so creative! :-D
My installation of Inkscape crashes when trying to open a previously saved file containing text of a sufficient length and a Linked Offset copy that has been scaled using the Edit Paths By Nodes tool and a stroke applied.
There are two files in the attached TAR: no-crash.svg (which doesn't crash Inkscape) and crash.svg (which does :-) ). The difference between the two files is that crash.svg has a longer string of characters in the original text object than does no-crash.svg (6 vs 7). They both have the same scale and stroke changes applied.
The non-crashing file took progressively longer to open while I was testing the length of text I could get away with before a crash occurred.
My machine was idling at 6% CPU, 14% RAM usage before launching the non-crashing file in Inkscape.
(Total RAM = 1.36GB with over 1GB free, running on a crappy old AMD Sempron 3600+)
$ time inkscape no-crash.svg
real 0m27.664s
user 0m21.492s
sys 0m4.400s
CPU, RAM usage jumps to 100%, 56% while Inkscape is opening the file.
It settled down to 6%, 18% after Inkscape finished loading the file.
I am using Inkscape 0.46 (Dec 31 2008), installed from the standard debian pool
Linux: Mepis (with a lot of Debian upgrades): 2.6.22-1-mepis-smp #1 SMP PREEMPT i686 GNU/Linux
The following error-log is written to the terminal when Inkscape crashes from opening the crash.svg file:
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.
terminate called recursively
Aborted
These tests were run by opening the files from the command line, however if the Open File dialog navigates to a directory containing the crash.svg file then Inkscape crashes as well. So, I guess this bug affects the preview code too.
I haven't tried this on the latest SVN version.
tags: | added: crash |
Changed in inkscape: | |
status: | Fix Committed → Fix Released |
confirmed with Inkscape 0.46+devel r22436 on OS X 10.5.8: Inkscape crashes (badly) already when reading the file for the thumbnail in the GtkFileChooser, for _both_ attached files.
error messages: bin:17308) : Gtk-WARNING **: Unable to find default local directory monitor type bin(17308, 0xa07f9720) malloc: *** mmap(size= 1207959552) failed (error code=12)
(inkscape-
inkscape-
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
terminate called after throwing an instance of 'std::bad_alloc'
what(): St9bad_alloc
Emergency save activated!
related to bug #414030 or rather: is bug #414030 a duplicate of this ;-) ?
"It looks as though the crash is related to the sequence in which svg elements are declared. The original file Ex.svg had the sequence : path, path, path, text. (where the paths all have an xlink:href reference to the text before it is declared.)"