moving an object to <defs> can segfault the app

Bug #1554562 reported by Alexander Sedov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Triaged
High
Unassigned

Bug Description

Steps to reproduce:
1. Make a graphical object.
2. Make a <use> element either via Clone (Alt-D) or manually.
3. Attempt to move an object over to <svg:defs> section.
4. Get a segmentation fault: ERROR:xml/simple-node.cpp:414:virtual void Inkscape::XML::SimpleNode::addChild(Inkscape::XML::Node*, Inkscape::XML::Node*): assertion failed: (!ref || ref->_parent == this)

Revision history for this message
Mc (mc...) wrote :

Can't reproduce. Which inkscape version/OS are you using ?

Revision history for this message
Alexander Sedov (alex0player) wrote : Re: [Bug 1554562] Re: moving an object to <defs> can segfault the app

Debian Stretch repository version (0.91). Once I get home, will try to
narrow it down more.
08 марта 2016 г. 18:45 пользователь "Mc" <email address hidden>
написал:

> Can't reproduce. Which inkscape version/OS are you using ?
>
> ** Attachment added: "out-4.ogv"
>
> https://bugs.launchpad.net/inkscape/+bug/1554562/+attachment/4592829/+files/out-4.ogv
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1554562
>
> Title:
> moving an object to <defs> can segfault the app
>
> Status in Inkscape:
> New
>
> Bug description:
> Steps to reproduce:
> 1. Make a graphical object.
> 2. Make a <use> element either via Clone (Alt-D) or manually.
> 3. Attempt to move an object over to <svg:defs> section.
> 4. Get a segmentation fault: ERROR:xml/simple-node.cpp:414:virtual void
> Inkscape::XML::SimpleNode::addChild(Inkscape::XML::Node*,
> Inkscape::XML::Node*): assertion failed: (!ref || ref->_parent == this)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/inkscape/+bug/1554562/+subscriptions
>

Revision history for this message
Alexander Sedov (alex0player) wrote :

Correction: after making a clone, apply any transformation to the clone (for example, move it), and then move the original to <defs>.

Revision history for this message
Alexander Sedov (alex0player) wrote :

Updated bug description, thank you!

Revision history for this message
jazzynico (jazzynico) wrote :

Not reproduced on Windows XP, Inkscape 0.48.5, 0.91 and trunk rev. 14696.

tags: added: crash xmleditor
Revision history for this message
Alexander Sedov (alex0player) wrote :

Unable to reproduce on Windows 8 as well. Still reliably reproducing on Debian stretch, v 0.91 r13725.

Revision history for this message
Mc (mc...) wrote :

Reproduced on Debian stretch, v 0.91-7+b1 , not reproduced on trunk 14696

Revision history for this message
jazzynico (jazzynico) wrote :

Not reproduced on Xubuntu 15.10, Inskcape 0.91-5ubuntu2 and trunk rev. 14696.

Libxml2 changed in stretch (2.9.3) and that new version might have revealed a bug in Inkscape.

Changed in inkscape:
importance: Undecided → High
milestone: none → 0.92
status: New → Confirmed
Revision history for this message
Mc (mc...) wrote :

Can anyone reproduce this with trunk ?

jazzynico (jazzynico)
Changed in inkscape:
status: Confirmed → Triaged
Revision history for this message
jazzynico (jazzynico) wrote :

Not reproduced on Xubuntu 16.04, Inkscape 0.91-7ubuntu2 and trunk rev. 14995 (libxml2-2.9.3).
@Mc-, it's weird I can't reproduce with 0.91 since we share (almost) the same Inkscape and libxml2 version (yes, I did move the clone before editing the object in the XML editor).

Revision history for this message
jazzynico (jazzynico) wrote :

@Alexander, could you please test again with the latest Inkscape stable in Stretch (you should now have a 0.91-9 version)?
Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.