Crash when interpolating two paths

Bug #1018338 reported by manWell
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
New
High
Unassigned

Bug Description

"Inkscape encountered an Internal error..." when applying the lessons of this tutorial (http://simarilius.wordpress.com/2006/10/21/faking-irregular-gradients-in-inkscape/) to a real document. Inkscape crashes at the time of interpolating as well as when I click a live preview. I am running inkscape 0.48 on an Intel Core (TM) i5-2400 CPU @ 3.10 GhZ with 7.98 Gb Usable RAM. Libgc 18 million with 7 mill slack for a total of 25 million (combined > 25 million)

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

> I am running inkscape 0.48 on an Intel Core (…)

Please provide more detailed information about which Inkscape version you have installed (see Inkscape menu 'Help > About Inkscape') and on which OS/platform you are using inkscape.

Does this crash also occur if you redo the tutorial in a new document based on the default template?
If the crash only occurs with some of your SVG files, please attach a sample one with the two paths which expose this issue when using the 'Interpolate' extension, along with the parameters set for it.

Changed in inkscape:
status: New → Incomplete
tags: added: crash extensions-plugins
Changed in inkscape:
importance: Undecided → High
Revision history for this message
manWell (maaktrans) wrote :

Inkscape 0.48.3.1 r9886

No, it doesnt occur in all files and I have managed it on a completely new file. So I tried to simplify the file I am working (less layers, etc) but it still crashes. I attach a copy of the file: the brown and yellow paths are meant to be interpolated

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

Reproduced with Inkscape 0.48.3.1 r9886 on OS X 10.7.4:
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_INVALID_ADDRESS at address: 0x00000000000001d8
> 0x00000001002412a8 in Inkscape::Extension::Implementation::Script::effect ()

Not reproduced with Inkscape 0.48.3.1 r9901 (0.48.x branch) and 0.48+devel r11515

Based on the version:
> Inkscape 0.48.3.1 r9886
and the id of <sodipodi:namedview> of the provided sample file:
> id="namedview3055"
this is another duplicate of a known regression in Inkscape 0.48.3.1:

Linking as duplicate to
Bug #944077 “inkscape crashed with SIGSEGV in Inkscape::Extension::Implementation::Script::effect()”
<https://bugs.launchpad.net/inkscape/+bug/944077>

Changed in inkscape:
status: Incomplete → New
Revision history for this message
manWell (maaktrans) wrote : Re: [Bug 1018338] Re: Crash when interpolating two paths

Where can I get Inkscape 0.48.3.1 r9901 for windows?

On 27/06/2012 13:12, ~suv wrote:
> *** This bug is a duplicate of bug 944077 ***
> https://bugs.launchpad.net/bugs/944077
>
> Reproduced with Inkscape 0.48.3.1 r9886 on OS X 10.7.4:
>> Program received signal EXC_BAD_ACCESS, Could not access memory.
>> Reason: KERN_INVALID_ADDRESS at address: 0x00000000000001d8
>> 0x00000001002412a8 in Inkscape::Extension::Implementation::Script::effect ()
> Not reproduced with Inkscape 0.48.3.1 r9901 (0.48.x branch) and
> 0.48+devel r11515
>
> Based on the version:
>> Inkscape 0.48.3.1 r9886
> and the id of <sodipodi:namedview> of the provided sample file:
>> id="namedview3055"
> this is another duplicate of a known regression in Inkscape 0.48.3.1:
>
> Linking as duplicate to
> Bug #944077 “inkscape crashed with SIGSEGV in Inkscape::Extension::Implementation::Script::effect()”
> <https://bugs.launchpad.net/inkscape/+bug/944077>
>
> ** Changed in: inkscape
> Status: Incomplete => New
>
> ** This bug has been marked a duplicate of bug 944077
> inkscape crashed with SIGSEGV in Inkscape::Extension::Implementation::Script::effect()
>

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

There has been no new newer stable release than 048.3.1 yet (the next planned bug.fix release will be 0.48.4, later this year).

See the last comment in bug #944077 for a workaround in Inkscape 0.48.3.1 with affected files.

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.