Just slice the 2nd Plate. Save your progress on EVERYTHING else before you do, though...
Actual results
Program nor computer crashed, the entire computer froze at 75% Sliced (Path Optimization) Consistently able to hard power off, reboot, and recreate with the same file. Video included in Google Drive folder link to demonstrate RAM monitoring. Sometimes slicing takes a while, but never takes RAM into infinity.
This is NOT a hardware issue: adjusting the objects in the plate layout stopped the issue. The only way I can figure is that THIS specific layout (or some other particular factor) caused the gcode path optimization algorithms to get in some kind of infinite loop and told the cpu it needed more and more and more RAM until everything froze, but not in a Blue Screen of Death way as one would expect. I'm VERY interested to see if anyone is able to recreate this issue with the same files. I have included the to exact original file (FREEZOMATIC.3mf) and a trimmed file with the one individual plate that broke everything (FREEZOMATIC3000.3mf) in the linked Google Drive folder.
Is there an existing issue for this problem?
OrcaSlicer Version
1.9.1
Operating System (OS)
Windows
OS Version
Windows 10 Home Ver. 22H2
Additional system information
Processor AMD Ryzen 5 5600X 6-Core Processor [3.70 GHz] Installed RAM 32.0 GB [4x8GB Corsair 2133MHz] MOBO ASRock B550 TaiChi System type 64-bit operating system, x64-based processor GPU NVIDIA 2080 SUPER 8GB
Printer
Bambu Lab P1S
How to reproduce
Download the FREEZOMATIC.3mf project file here:
https://drive.google.com/drive/folders/1oDmdp9GQts9OYDnIxfCvjqqmHYzMTRyf?usp=sharing
Just slice the 2nd Plate. Save your progress on EVERYTHING else before you do, though...
Actual results
Program nor computer crashed, the entire computer froze at 75% Sliced (Path Optimization) Consistently able to hard power off, reboot, and recreate with the same file. Video included in Google Drive folder link to demonstrate RAM monitoring. Sometimes slicing takes a while, but never takes RAM into infinity.
Expected results
Normal slicing and gcode optimization.
Project file & Debug log uploads
https://drive.google.com/drive/folders/1oDmdp9GQts9OYDnIxfCvjqqmHYzMTRyf?usp=sharing
Checklist of files to include
Anything else?
This is NOT a hardware issue: adjusting the objects in the plate layout stopped the issue. The only way I can figure is that THIS specific layout (or some other particular factor) caused the gcode path optimization algorithms to get in some kind of infinite loop and told the cpu it needed more and more and more RAM until everything froze, but not in a Blue Screen of Death way as one would expect. I'm VERY interested to see if anyone is able to recreate this issue with the same files. I have included the to exact original file (FREEZOMATIC.3mf) and a trimmed file with the one individual plate that broke everything (FREEZOMATIC3000.3mf) in the linked Google Drive folder.