Segfault in SeamPlacer

[I1138]

What happened?

SuperSlicer v2.5.60.0 (sourced via archlinux AUR, which uses the ubuntu_20.04 appimage) segfaults while trying to slice some stls.

Attached log:

superslicer --loglevel 5
... trimmed, can provide if needed.
[2025-02-15 16:26:37.907374] [0x0000718985ff86c0] [debug]   SeamPlacer: Compute visiblity sample points: end
[2025-02-15 16:26:37.907384] [0x0000718985ff86c0] [debug]   SeamPlacer: Mesh sample raidus: 1.91811
[2025-02-15 16:26:37.907387] [0x0000718985ff86c0] [debug]   SeamPlacer: build AABB tree: start
[2025-02-15 16:26:37.908316] [0x0000718985ff86c0] [debug]   SeamPlacer: build AABB tree: end
[2025-02-15 16:26:37.908323] [0x0000718985ff86c0] [debug]   SeamPlacer: raycast visibility of 30000 samples over 5932 triangles: end
[2025-02-15 16:26:37.993121] [0x0000718985ff86c0] [debug]   SeamPlacer: raycast visibility of 30000 samples over 5932 triangles: end
[2025-02-15 16:26:37.993135] [0x0000718985ff86c0] [debug]   SeamPlacer: gather_seam_candidates: start
Segmentation fault (core dumped)

This doesn't happen for some stls, and appears to not be dependent on any particular setting preset. This seems to be different than other segfault issues on this repo that referenced being able to work around the issue by changing perimeter generation.

I've not been able to identify any variation of seam settings that prevent the segfault.

If it proves difficult to reproduce it on your side, it's possible I can stick gdb or valgrind on it / send you a core file from the segfault.

Project file & How to reproduce

broom-brace.3mf.zip
CC0 if you want to use it in a test / etc.

To reproduce with above: Load, click Slice now.

Version

2.5.60.0

Operating system

Archlinux (rolling release, but using an appimage so it probably doesn't matter)

Printer model

Ender3 V2, klipper