Crash after select normal path object

[Roul P.]

I used beta version 0.48+devel r13349. (on Win 7)

[Roul P. (perhelion1)]

I've extracted only the relevant blue object.

[jazzynico (jazzynico)]

Reproduced on Windows XP, Inkscape 0.48.4 and trunk revision 13395.
Steps:
1. Open the file attached comment #2.
2. Open the XML editor.
3. In the XML editor, select the g with id="g77".
4. Move a selection handle.

No bt, but the following console message:
----
** (inkscape.exe:844): WARNING **: The snapmanager has been set up before, but unSetup() hasn't been called afterwards.
It possibly held invalid pointers
Assertion failed: this->is_initialized(), file d:\Dev\devlibs/include/boost/optional/optional.hpp, line 590

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

Program exited with code 03.
----

I'll try to get a valid trace on Crunchbang Waldorf later today.

[jazzynico (jazzynico)]

Note that the path with id="path79" is linked to an empty clip-path (url(#SVGID_3_)).
Removing the clip-path attribute with the XML editor solves the issue.

[jazzynico (jazzynico)]

Also reproduced on Crunchbang Waldorf, Inkscape 0.48.3.1 (trace attached).
I can't reproduce it with the trunk because the handles are hidden when selecting the affected object from the XML editor...

[boussad (picks)]

U really have to fix crashes GGG!
I already start to feel annoying about this league. It's just impossible to finish a map without crashing 1 or 2 times with a molten strike build!

see: https://bluestacks.vip/ , https://kodi.software/ & https://luckypatcher.pro/

[Jonathan Hofinger (jhofinger)]

Not replicated with the instructions from #3 in Inkscape 0.92.4, as well as Inkscape 1.1-dev (c990a67, 2020-04-09), Windows 10. In both cases, selecting the group doesn't show any handles on canvas, probably due to the empty clip-path. Please reopen on http://inkscape.org/report if the problem occurs again.

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