lpe path and point parameter incompatibility

Bug #275231 reported by jfb
2
Affects Status Importance Assigned to Milestone
Inkscape
Invalid
Undecided
Unassigned

Bug Description

lpe-test-doEffect-stack of svn revision 19916 show a bug concerning path and point parameters:

Add this effect to some object. Node-edit the path parameter. Exit node-edit mode. Move the object around. Inkscape crashes when you release the mouse.
[segmentation fault in strcmp() in msvcrt.dll] :-(

Remark1: If you comment out the relevant lines to remove either the path or the point parameter: no crash at all.

Remark2: if you edit the path parameter in xml editor, no crash occurs.

I had some look at it, and did follow execution up to some point where I'm lost:
When you move the object around, "transform_multiply" is called for each parameter. At the path's (or point's, depends who is registered first) turn, this write to repr and hence triggers an event calling "on_repr_attr_changed".
The crash happens right after that one, but before returning to "transform_multiply", so I don't know where :-(

I guess knotholders/knotholderentities are somehow aware of the change and might be responsible for the crash, but I don't understand how atm. This goes too deep in inkscape/lpe machinery for me to catch it without someone's help...

Anyway, no hurry: No lpe uses both paths and points param in the code base atm; I wanted to in vonKoch, but will try to use a path instead!
JF.

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

not reproduced with Inkscape 0.47+devel r9096 on OS X 10.5.8 - has this been fixed?

tags: added: crash
Changed in inkscape:
status: New → Incomplete
Revision history for this message
su_v (suv-lp) wrote :

Closing due to lack of feedback. Please reopen if this was done in error and the crash still occurs in the latest stable release or current development snapshots.

(Not reproduced with Inkscape 0.48+devel r10298 on Mac OS X 10.5.8 (i386))

Changed in inkscape:
status: Incomplete → Invalid
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.