Gabe-H
commented
1 month ago Am experiencing this too. Running on a fresh install of SuperSlicer, with the default Voron 2.x 350 configuration (cleared AppData\Roaming\SuperSlicer to ensure new configuration). Can slice the built in Box model, cannot slice the built in Rabbit model. I also get the occasional "Access violation" error, as well as no crash_log.txt generated. (Almost lost my mind searching for it.
I did find that a file ".####.gcode.tmp" is generated in AppData\Local\Temp, but it contains just the base64 text for the png thumbnails. No actual GCode.
What happened?
When slicing specific models, in my case this one (rotated upright), superslicer crashes during the "Generating perimeters" stage. Sometimes there is a split second where a popup briefly opens, saying "SuperSlicer has encountered a fatal error: "Access (status) violation", but it immediately closes with the entire program crashing.
Project file & How to reproduce
After resetting many options in my print configuration to default, i could narrow it down to a combination of two settings. When the Arachne Perimeter generator is enabled and the Perimeters & Shell > Overhangs > Bridge speed and fan is set very low (below around 23% for me).
Attached is a 3mf file, which upon slicing will crash superslicer. It contains a very small slice of the model, to which i narrowed down the layer that causes the crash. There is no
crash_log.txtfile generated. For easy reproduction, i used the default "Original Prusa MINI & MINI+" template, with only the "Max layer height" of extruder 1 increased to 0.4, since the print settings first layer height is by default 75%.reproduce.zip
This was tested on these versions:
Version
Nightly build: https://github.com/supermerill/SuperSlicer/actions/runs/9837348764
Operating system
Windows 11
Printer model
No response