Error when undoing a "cut path" operation

[Domus]

I create two rectangles, select them both, then do a "cut path."

A subsequent undo (ctrl-z) triggers an error and the application closes.

Version 0.91 r13725 on Windows Vista-32

[su_v (suv-lp)]

Crash not reproduced with Inkscape 0.91 r13725 on OS X 10.7.5 based on the available 'steps to reproduce'.

Could you please attach a test case (Inkscape SVG file) with objects which consistently reproduce this crash on undo?

[su_v (suv-lp)]

Note: similar bug existed in earlier prerelease versions (0.91pre2) but was later fixed:
- Bug #1380413 “crash on rectangle union, undo”

[Domus (dominique-domussoft)]

Apparently the rectangles need to intersect for this to happen. It happens every single time, without exception.

[su_v (suv-lp)]

I tried with intersecting rects (otherwise 'Path > Cut' would not make sense to be applied), still can't reproduce.

Could you please check the installed version of Inkscape?

[su_v (suv-lp)]

Not reproduced with Inkscape 0.91 r13725 (64bit MSI installer) on Windows 7 (64bit) either.

[Domus (dominique-domussoft)]

Re-installed InkScape. Fired it up, drew two intersecting rectangles (works with other shapes too), selected both, "Path" -> "Cut path," then ctrl-Z.

Dialog box with "Microsoft Visual C++ Runtime Library" caption pops up, with text "This application has requested the Runtime to terminate in an unusual way. Please contact the application's support team for more information."

[Liam P. White (liampwhite)]

Also not reproduced on Ubuntu 14.04.2 with Inkscape 0.91 r13731 and Inkscape 0.91+devel r13936.

[Liam P. White (liampwhite)]

It might be helpful for you to attach your preferences.xml file (%APPDATA%\inkscape\preferences.xml)

[Domus (dominique-domussoft)]

Preferences attached.
I'd feel quite bad if I wasted you lads' time.

[Liam P. White (liampwhite)]

Successfully reproduced on Ubuntu 14.04.2 with the attached preferences.xml file.

**
ERROR:../../src/document-undo.cpp:158:static void Inkscape::DocumentUndo::maybeDone(SPDocument*, const gchar*, unsigned int, const Glib::ustring&): assertion failed: (doc->priv->sensitive)

Attaching backtrace.

[Domus (dominique-domussoft)]

Any idea what setting I might have screwed up? I don't really recall changing any after installing the latest version.

[Alvin Penner (apenner)]

also reproduced on Windows 7, 32 bit, Inkscape 0.91 using above preferences file, exit messages below:

C:\Program Files\Inkscape>inkscape
**
ERROR:src/document-undo.cpp:158:static void Inkscape::DocumentUndo::maybeDone(SP
Document*, const gchar*, unsigned int, const Glib::ustring&): assertion failed:
(doc->priv->sensitive)

Emergency save activated!

[su_v (suv-lp)]

Crash can be avoided by removing these attributes from the rect current style (eventcontext) in the prefs file:
 "marker-start:none;marker-mid:none;marker-end:none;"
(using an external editor).

Likely related: Bug #1372151: "0.91 pre2 redo button doesn't work", comment 13, 14, 17

[Alvin Penner (apenner)]

@Domus, I see your preferences file says:
version="0.45.1"
Was that your previous version of Inkscape?

[Domus (dominique-domussoft)]

@Alvin, That's odd. Version prior to 0.91 was 0.48.

I did notice that my recently accessed file list was often not up to date either. Maybe that's related.

[Alvin Penner (apenner)]

actually, in light of comment 13 by ~suv, the version probably doesn't matter, just ignore it

[Domus (dominique-domussoft)]

@~suv Works like a charm. Many thanks!

[su_v (suv-lp)]

Same workaround also effective to avoid crash reported in
* Bug #1449276 “Crash on Undo of Break apart with Fill+Stroke Dialog open”
  https://bugs.launchpad.net/inkscape/+bug/1449276

[su_v (suv-lp)]

Does not reproduce with Inkscape < 0.91 (e.g. 0.48.5).

[Rajinder Yadav (rajinder-yadav)]

This bug still exists for me in 0.92.4 on Kubuntu 18.04.

On a fresh open, create a circle with a line, select all, perform a cut, undo and get a crash.

[Alvin Penner (apenner)]

- reproduced on Windows 10, Inkscape 0.92.4 (5da689c313, 2019-01-14)
- not reproduced on Windows 10, Inkscape 1.0alpha (12c5988, 2019-01-17)

[Alvin Penner (apenner)]

backtrace on 92.4:

Program received signal SIGSEGV, Segmentation fault.
0x6fefc8f1 in ?? () from c:\program files (x86)\inkscape\libstdc++-6.dll
(gdb) bt
#0 0x6fefc8f1 in ?? () from c:\program files (x86)\inkscape\libstdc++-6.dll
#1 0x01717f30 in libinkscape_base!_Z23sp_button_new_from_dataN8Inkscape8IconSizeE12SPButtonTypePNS_2UI4View4ViewEPKcS7_ ()
   from c:\program files (x86)\inkscape\libinkscape_base.dll
#2 0x017a6249 in libinkscape_base!_Z27sp_paintbucket_toolbox_prepP9SPDesktopP15_GtkActionGroupP8_GObject ()
   from c:\program files (x86)\inkscape\libinkscape_base.dll
#3 0x017a677f in libinkscape_base!_ZN8Inkscape3XML21CompositeNodeObserver22notifyAttributeChangedERNS0_4NodeEjNS_4Util10ptr_sharedIcEES6_ () from c:\program files (x86)\inkscape\libinkscape_base.dll
#4 0x08c51000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) c
Continuing.
[New Thread 49920.0xc5d0]

Program received signal SIGSEGV, Segmentation fault.
0x6fefc8f1 in ?? () from c:\program files (x86)\inkscape\libstdc++-6.dll
(gdb) c
Continuing.
[Inferior 1 (process 49920) exited with code 030000000005]

[Qantas94Heavy (qantas94heavy)]

This appears to be the same bug as bug 1809676, closing as duplicate. Please let us know if this is not the case, thanks.

Closed by: https://gitlab.com/Qantas94Heavy