Archived issue #0025916
Modeling Algorithms - Exception during execution thickening of shell
Description
There are exceptions if test cases after command thickshell.
bugs modalg_2 bug21261_15:
...
...
bugs modalg_2 bug21261_21
...
...
bugs modalg_2 bug21261_15:
...
Draw[]> thickshell res s -5 An exception was caught 5D74E4AC : Standard_ConstructionError: Offset with no C1 Surface ** Exception ** 5D74E4AC : Standard_ConstructionError: Offset with no C1 Surface
...
bugs modalg_2 bug21261_21
...
Draw[17]> thickshell res s -5 An exception was caught 5D74E4AC : Standard_ConstructionError: BRepOffset_MakeOffset : Incorrect set of faces to remove, the remaining shell is not connected ** Exception ** 5D74E4AC : Standard_ConstructionError: BRepOffset_MakeOffset : Incorrect set of faces to remove, the remaining shell is not connected
...
Steps to reproduce
test bugs modalg_2 bug21261_15 bug21261_21
Public activity
6 archived notes
Participants are labeled by their role within this record.
Problem described in issue is reproduced on current state of OCCT.
Analyze, please the issue.
Rules to be used you can find in public documentation (chapter "Developers Guides):
https://www.opencascade.com/doc/occt-7.4.0/overview/html/occt_dev_guides__contribution_workflow.html
Rules to be used you can find in public documentation (chapter "Developers Guides):
https://www.opencascade.com/doc/occt-7.4.0/overview/html/occt_dev_guides__contribution_workflow.html
Sergey, I assigned it back to you as Nikolay is no longer available to work on this task.
Test case bugs modalg_2 bug21261_15 is OK in current version.
Test case bugs modalg_2 bug21261_21 has no exception: in BRepOffset_MakeOffset exist exit code for not connected shells.
Test case bugs modalg_2 bug21261_21 has no exception: in BRepOffset_MakeOffset exist exit code for not connected shells.
Andrey, if issue is not reproducible on current master, please first check in which OCCT release it has been fixed to set properly "Fixed in Version"
(ideally, it is desired also finding the patch which has solved the issue).
(ideally, it is desired also finding the patch which has solved the issue).
Current bug was fixed by two branches: #26556 and #31735