PrusaSlicer CLI on MacOS (ARM) segmentation faults on --merge flag

[kevinvalk]

Description of the bug

Whenever I use the command line to automatically export gcode I was having segmentation faults. I narrowed this down to the --merge flag and it seems to be model independent. So a /Applications/PrusaSlicer.app/Contents/MacOS/PrusaSlicer --merge 3dbenchy.stl triggers a segmentation fault. That said, adding a --dont-arrange allows for loading the GUI.

/Applications/PrusaSlicer.app/Contents/MacOS/PrusaSlicer --merge 3dbenchy.stl

/Applications/PrusaSlicer.app/Contents/MacOS/PrusaSlicer --dont-arrange --merge 3dbenchy.stl

The plot does thickens, as adding an --export-gcode while also having --dont-arrange crashes on the more complex CLI invocation, but I have a hard time narrowing down what the exact combinations are...

Project file & How to reproduce

1. Download a model
2. Run the following command from CLI (on a Mac maybe ARM chip) /Applications/PrusaSlicer.app/Contents/MacOS/PrusaSlicer --merge 3dbenchy.stl
3. Observe segmentation fault

Checklist of files included above

• Project file
• Screenshot

Version of PrusaSlicer

2.9.2

Operating system

Apple M1 Max - macOS Sequoia 15.4.1

Printer model

MK4s