Exporting an assembly as STEP crashes FreeCAD

[prokoudine]

Exporting an assembly as STEP crashes FreeCAD

[prokoudine]

@PaddleStroke Is this up your alley?

[maxwxyz]

I cannot reproduce on

OS: Windows 10 build 19045
Word size of FreeCAD: 64-bit
Version: 0.22.0dev.37669 (Git)
Build type: Release
Branch: main
Hash: 3b4598ce04d7aaec69feeb560c29ae18f0236e0c
Python 3.11.9, Qt 5.15.13, Coin 4.0.2, Vtk 9.2.6, OCC 7.7.2
Locale: German/Germany (de_DE)
Installed mods: 
  * CurvedShapes 1.0.9
  * Curves 0.6.36
  * fasteners 0.5.21
  * OpenTheme 2024.5.16
  * OpticsWorkbench 1.0.17
  * sheetmetal 0.4.14

[PaddleStroke]

Cannot reproduce either on win10.

[maxwxyz]

@prokoudine could you provide an example file where this is reproducible? Maybe one body is broken.

[prokoudine]

Er, I already did provide?

[maxwxyz]

ah sorry, wrong issue. As I said I cannot reproduce this unfortunately.

[prokoudine]

It seems to be Linux-specific. Another Linux user reported this on Ondsel's Discord.

[PaddleStroke]

Can the same bug be reproduced with a App::Part instead of an assembly?

[liamhays]

I can confirm this issue on Linux with that specific file, once you download all the other files that are part of the assembly. However, loading the assembly also causes this sequence of errors in report view (visible in OP's report):

13:14:41  pyException: <string>(2)<class 'AttributeError'>: Module __main__ has no class MotorObserver
13:14:41  pyException: <string>(2)<class 'AttributeError'>: Module __main__ has no class MotorObserver
13:14:41  pyException: <string>(2)<class 'AttributeError'>: Module __main__ has no class MotorObserver

and I wonder if those are causing the problem. Specs:

OS: Arch Linux (KDE)
Word size of FreeCAD: 64-bit
Version: 0.22.0dev.37730 (Git) AppImage
Build type: Release
Branch: main
Hash: 30f7f2688921e6e5242beaa9d71e0fdd844b20e3
Python 3.11.9, Qt 5.15.13, Coin 4.0.2, Vtk 9.2.6, OCC 7.7.2
Locale: English/United States (en_US)

On the actual export, this is printed on both systems (could also be the error source, especially if it's caused by broken bodies):

<Import> ExportOCAF2.cpp(387): deltarobot_example#Joints has null shape

and then a segmentation fault occurs, crashing the application. On Windows (specs below), a segfault also occurs, but something catches it and makes a little dialog that says "Export failed: Access violation". Clicking OK closes the dialog and FreeCAD doesn't crash. Windows specs:

OS: Windows 10 build 19045
Word size of FreeCAD: 64-bit
Version: 0.22.0dev.37730 (Git)
Build type: Release
Branch: main
Hash: 30f7f2688921e6e5242beaa9d71e0fdd844b20e3
Python 3.11.9, Qt 5.15.13, Coin 4.0.2, Vtk 9.2.6, OCC 7.7.2
Locale: English/United States (en_US)

[prokoudine]

and I wonder if those are causing the problem

Most unlikely, because the original report came from a user who wasn't using MotorObserver. In fact, he was using a completely different assembly.