Instant Crash upon editing a path within a clipped group within a larger clipped group

Bug #1676611 reported by Reptorian
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
New
High
Unassigned

Bug Description

As attached in the file, if you edit the bounding box of path6764 found in Side Shoe> Shoe Render [Biggest Object is used for clipping] > Sole Sections[Sections of the biggest object or that contains part of the biggest object is clipped] > Sole Sections 3 [sections of the object that comes before this is used as clipping shape], Inkscape will instantly terminate. So, to replicate the crash without the file, you must create series of object which seems to match the following format

1. Layer
 -a. Group of Groups [Largest object clipped ]
  --I. Group A [Clipped Section containing several clipped group]
   ---A. Subgroup A of Group A [Clipped Group]
   ---B. Subgroup B of Group A [Clipped Group]
   ---C. Subgroup C of Group A [Clipped Group]
  --II. Group B [Clipped Group]

After that, please select a object within Subgroup A, and move the bounding box to see Inkscape crash.

System and Program utilized - Inkscape 0.92.0 r15299 inside Windows 10 x64 Home Edition

Additional Information - Threads:8 & Render Cache : 256

I don't think this bug has been seen before. It's quite new, but I would think that it really needs to be looked into as this is the best approach to rendering within Inkscape.

Tags: clipping crash
Revision history for this message
Reptorian (reptillia-39) wrote :
Revision history for this message
Reptorian (reptillia-39) wrote :

Also, changing the path fill fixes the problem.

jazzynico (jazzynico)
Changed in inkscape:
importance: Undecided → High
tags: removed: bounding box
Revision history for this message
Nathan Lee (nathan.lee) wrote :

I could not replicate this issue in 0.92.0 r15299 (Windows 10) with the given file.

You mention that changing the path fill fixes the problem, so I'm guessing that the clipping group structure isn't the minimal requirements for causing this issue though.

If you have time and this is still occurring in the current version of Inkscape, could you file this report in our new bugtracker on Gitlab (see https://inkscape.org/contribute/report-bugs/)? (Of course, just add the info here if you don't have time).

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.