Pattern Along Path LPE breaks namedview assertion

Bug #1484009 reported by Parcly Taxel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
New
Undecided
Unassigned

Bug Description

The attached file causes trunk Inkscape (r14285) to crash on Trisquel 7.0 with the following message:

**
ERROR:../../src/sp-namedview.cpp:1053:SPNamedView* sp_document_namedview(SPDocument*, const gchar*): assertion failed: (nv != NULL)
Aborted

When I try with other paths with a Pattern Along Path LPE applied, the bug does not appear and the file loads normally.

Revision history for this message
Parcly Taxel (parclytaxel-deactivatedaccount) wrote :
su_v (suv-lp)
tags: added: crash
Revision history for this message
su_v (suv-lp) wrote :

On OS X 10.7.5:
- not reproduced with 0.91 r13725,
- reproduced with 0.91+devel r14285:

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000
0x00000001007f0f87 in Geom::force_continuity ()

Based on tests with archived builds:
- not reproduced with rev 14224,
- reproduced with rev >= 14228;
likely a regression introduced with the latest 2geom update in r14226:
https://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/14226

Based on the path geometry, and the backtrace (see attached), this is likely the same issue as already reported in
* Bug #1482806 “crash if Pattern-along-Path LPE applied to path with horizontal line segment (rev >= 14226)”
  https://bugs.launchpad.net/inkscape/+bug/1482806

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

Proposing to link as duplicate to bug #1482806.

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

Crash not reproduced with Inkscape 0.91+devel r14293+patch from bug #1482806 - taking this as confirmation that the two reports share the same underling issue, and linking as duplicate to bug #1482806.

Feel free to add a comment here (bug #1484009) and revert the duplicate status if you disagree and think this was done in error.

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.