Inkscape crashes when dragging certain objects in XML Editor

Bug #1803481 reported by Tristan Bailey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Fix Released
Undecided
Unassigned

Bug Description

Steps to reproduce crash/bug:

1. Open a new document in Inkscape.
2. Create two objects of your choosing on the canvas.
3. Open the XML Editor pane (Edit > XML Editor...)
4. With the group element marked as "Layer1" (the fifth object in the list), click and drag it down the list, then release (it shouldn't move anywhere)
5. In the same list, click and drag the first object that you made, up above the group object, and release.
6. Repeat step 5 with the other object that you made. Inkscape will crash.

Notes:

 - It doesn't appear to matter which type of objects you create to begin with.
 - It doesn't appear to matter how many objects you create, provided it is more than one.
 - It doesn't appear to matter in which order the objects are shifted above the group element in the list, Inkscape will always crash after moving the second object of your choosing in the list up (not necessarily the second that you created to begin with).
 - It doesn't need to be the group element that is dragged first, as the bug occurs after dragging other elements above the objects you made, down (e.g. meta object, sodipodi named view, etc.), and then dragging the objects you created up.

This bug destroyed over an hour's work on an image I was making; please fix.

Inkscape 0.92.3 (2405546, 2018-03-11)
Windows 8.1

Tags: crash
tags: added: crash
description: updated
Revision history for this message
Alvin Penner (apenner) wrote :

reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)

backtrace:
Program received signal SIGTRAP, Trace/breakpoint trap.
0x74d4b1a3 in KERNELBASE!DeleteAce () from C:\WINDOWS\SysWOW64\KernelBase.dll
(gdb) bt
#0 0x74d4b1a3 in KERNELBASE!DeleteAce () from C:\WINDOWS\SysWOW64\KernelBase.dll
#1 0x68828b59 in ?? () from c:\program files (x86)\inkscape\libglib-2.0-0.dll
#2 0x68819bb5 in ?? () from c:\program files (x86)\inkscape\libglib-2.0-0.dll
#3 0x68819c36 in ?? () from c:\program files (x86)\inkscape\libglib-2.0-0.dll
#4 0x01688599 in libinkscape_base!_ZN8Inkscape3XML10SimpleNode8addChildEPNS0_4NodeES3_ ()
   from c:\program files (x86)\inkscape\libinkscape_base.dll
#5 0x016634ee in libinkscape_base!_Z14on_row_changedP13_GtkTreeModelP12_GtkTreePathP12_GtkTreeIterPv ()
   from c:\program files (x86)\inkscape\libinkscape_base.dll
#6 0x0066ec00 in ?? ()
#7 0x61a4f8a0 in ?? () from c:\program files (x86)\inkscape\libgtk-win32-2.0-0.dll
Cannot access memory at address 0x40000006
(gdb) c
Continuing.
[Inferior 1 (process 7892) exited with code 03]

Changed in inkscape:
status: New → Confirmed
Revision history for this message
Alvin Penner (apenner) wrote :

reproduced on Windows 10, Inkscape 0.92+devel (bac5395, 2018-11-10)

backtrace:
Program received signal SIGTRAP, Trace/breakpoint trap.
0x74d4b1a3 in KERNELBASE!DeleteAce () from C:\WINDOWS\SysWOW64\KernelBase.dll
(gdb) bt
#0 0x74d4b1a3 in KERNELBASE!DeleteAce () from C:\WINDOWS\SysWOW64\KernelBase.dll
#1 0x64c2ca59 in ?? () from c:\app\temp\inkscape_devel\libglib-2.0-0.dll
#2 0x64c1d835 in ?? () from c:\app\temp\inkscape_devel\libglib-2.0-0.dll
#3 0x64c1d8e6 in ?? () from c:\app\temp\inkscape_devel\libglib-2.0-0.dll
#4 0x02047c6c in libinkscape_base!_ZN8Inkscape3XML10SimpleNode11removeChildEPNS0_4NodeE ()
   from c:\app\temp\inkscape_devel\libinkscape_base.dll
#5 0x020212f3 in libinkscape_base!_Z14on_row_changedP13_GtkTreeModelP12_GtkTreePathP12_GtkTreeIterPv ()
   from c:\app\temp\inkscape_devel\libinkscape_base.dll
#6 0x0065ec0c in ?? ()
#7 0x00000000 in ?? ()
(gdb) c
Continuing.
[Inferior 1 (process 12204) exited with code 03]

Revision history for this message
TylerDurden (8thrule) wrote :

Not reproduced with Inkscape 0.92.2 (5c3e80d, 2017-08-06), Win 8.1-64

Revision history for this message
Tristan Bailey (tristanlbailey) wrote :

This is still reproducible in Inkscape 0.92.4 (5da689c313, 2019-01-14), Win 8.1-64

Revision history for this message
Alvin Penner (apenner) wrote :

since Inkscape is moving its bug tracking system to GitLab it might be best to re-issue this report at:
https://gitlab.com/inkscape/inbox/issues

sorry for the inconvenience.

Revision history for this message
Nathan Lee (nathan.lee) wrote :

Tristan Bailey (OP) has moved the issue already (see https://gitlab.com/inkscape/inkscape/issues/118). So closing this issue as part of bug migration (also fix committed :-))

Changed in inkscape:
status: Confirmed → Fix Committed
Max Gaukler (mgmax)
Changed in inkscape:
status: Fix Committed → Fix Released
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.