Inkscape crashes with Non-contiguous path ../../src/2geom/path.cpp:987

Bug #1541893 reported by Filip Dominec on 2016-02-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Undecided
Unassigned

Bug Description

When I open the attached document in Inkscape 0.91 on my computer (Ubuntu vivid, Linux 3.19.0-26-generic x86_64), enable the guide snapping and move the rectangles randomly, Inkscape terminates at once. Note I originally edited the file manually, possibly leaving two guides of the same ID, but it seems fixed now by inkscape.

When crashing, inkscape writes out in the terminal:

filip@chrudos:~ $ inkscape
/home/filip/byt.svg:36: parser error : Attribute inkscape:cy redefined
     inkscape:window-maximized="0">
                                  ^
terminate called after throwing an instance of 'Geom::ContinuityError'
  what(): lib2geom exception: Non-contiguous path (../../src/2geom/path.cpp:987)

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.
Aborted (core dumped)

su_v (suv-lp) wrote :

<off-topic>
I would recommend to reconsider the tool(s) which have been used to manually edit the SVG file - check the lines 243-244, 247-248, 268-285 in the SVG source of the file attached to the report - these lines do not really look like valid or meaningful SVG code to me (?) ... mishap on manual editing / copy&paste?
</off-topic>

Crash so far not reproduced with Inkscape 0.91 r13725 on OS X 10.7.5, based on the available information (I assume that you use snapping of cusp nodes to guides when dragging an arbitrarily selected rectangle with the select tool?).

tags: added: crash snapping
su_v (suv-lp) wrote :

This provided information conflicts:
On 2016-02-04 16:24 (+0100), Filip Dominec wrote:
> When I open the attached document in Inkscape 0.91 on my computer

and from the SVG file:
> inkscape:version="0.91+devel r"

If you have the unstable devel version installed (instead of the stable release Inkscape 0.91 r13725), then likely this report could be a duplicate of or at least closely related to the recent regression in trunk tracked in
* Bug #1541727 “Inkscape crash while doing an activity”
  https://bugs.launchpad.net/inkscape/+bug/1541727
The trigger in bug #1541727 is though _scaling_ (stretching) a rectangle which is snapped with the opposite corner to a guide, not _moving_ (as indicated in the bug description here (bug #1541893).

Could you please clarify which version of Inkscape you actually have installed, and provide more details about how to trigger the reported crash?

Changed in inkscape:
status: New → Incomplete
Filip Dominec (fdominec) wrote :

~suv, you are right, my version is in fact "0.91+devel r".

The description for the error circumstances looks very likely to be also my case, it is triggered by resizing and snapping with the opposite corner. Sorry for being imprecise, now I understand it may be an important difference for tracing the bug.

Filip Dominec (fdominec) wrote :

It appears that I have reported a known bug, existing in the devel version. Therefore the bug report is void.

If I can help in any way, leave me a message. Thank you for your hard work on Inkscape!

su_v (suv-lp) wrote :

Thank you for reporting back - based on your further information, it seems quite safe to assume that you encountered the same regression as reported earlier today in bug #1541727. I have updated the bug summary line of that earlier report to better describe the issue, and will link this report as duplicate to bug #1541727.

Feel free to add a comment to bug 1541727 in case important details about steps to reproduce or about the scope of the regression is missing (the developer for Inkscape's snapping feature has already been notified, and usually can address such regressions rather quickly - as time permits, ofc).

Changed in inkscape:
status: Incomplete → New
tags: added: regression
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers