Thanks for reporting back @Lohi - the fact that you get the same stack trace on an intel mac as I see on the M2 mac, but isn’t seen on windows/linux, indicates perhaps it’s something to do with the Apple compilers or something else to be determined. Hopefully with more debugging we’ll get to the bottom of it. Please try these instructions for capturing the program state so you can share it if a crash occurs.
And yes, Slicer is a UI/UX minefield. Just so you know, we have limited developer resources so we draw an arbitrary line and say that any hardware over 5 years old should be considered unsupported, so your 10 year old mac mini is way out of spec for current Slicer. Still, we’d like it to work anyway and it’s helpful for debugging, but it may never be usable with the latest releases. A newer computer might save you some frustration.
Regarding translating the object (or for Slicer, the camera) on a mac with a trackpad you press shift and then use the trackpad click-and-drag motion. A three-button mouse is highly recommended if you are doing a lot of interactive visualization and segmentation.