Slicer crashes during gcode generation

[rcmaniac25]

Description of the bug

I loaded a multi-color painted model (https://www.myminifactory.com/object/3d-print-bamboo-dragon-cinderwing3d-x-bambulab-354514) and after setting up with the desired print settings, waited for it to slice. During the generating g-code stage, the slicer simply closed.

Project file & How to reproduce

1. Get the files from https://www.myminifactory.com/object/3d-print-bamboo-dragon-cinderwing3d-x-bambulab-354514
2. Load in the "MMU_Prusa.3mf" version. If you try to open this as a project, it will simply load the model. So make sure to have the MMU printer selected or it will show up as single color.
3. Update every object to have wipe into infill
4. Let it slice

Project (only plate 1 has the issue. Plate 2 does not have the issue)
Bamboo Dragon-Upload.zip

Screen visual

Checklist of files included above

• Project file
• Screenshot

Version of PrusaSlicer

Version 2.9.0

Operating system

Windows 10

Printer model

Prusa MK4S+MMU3

[rcmaniac25]

Minor update: I tried to slice this some 5+ times and it crashed every time. I opened it again, took the screenshot, and then wrote this ticket. When I finished... it had finished slicing without crashing. I spent the next hour or so trying to figure out what situation let it slice without crashing and could not figure it out. Not sure if sometimes it works, but the only time it sliced without crashing was after a screenshot and writing this ticket... if I have a moment, I'll try again to see if I can get a "crashes all the time EXCEPT..." case

[murk-sy]

If I had to guess it sounds like you have an 13th/14th gen Intel processor.

The reason it didn't crash once is (I believe) the fact that it went from a highly multithreaded to highly singlethreaded workload very quickly. If you sliced while running something else CPU intensive (like Prime95 stress test or something) I believe you should be able to slice reliably.

Check these:

• https://community.intel.com/t5/Blogs/Tech-Innovation/Client/Intel-Core-13th-and-14th-Gen-Desktop-Instability-Root-Cause/post/1633239
• https://www.intel.com/content/www/us/en/download/15951/intel-processor-diagnostic-tool.html

Duplicate issues:

• Slicer crashes when generating organic supports on this model #13483
• 2.7.2 Internal Error: Access violation #12387
• Crash when slicing (2.7.2-alpha2) #12236
• Error Prusaslicer #12671

[rcmaniac25]

If I had to guess it sounds like you have an 13th/14th gen Intel processor.

6th Gen Intel

[murk-sy]

The one time I predict it's a 14th gen thing without explicitly testing it ends up being not the problem... bah humbug

Reproducible reliably, I'll try to see if I can minimise the issue to fewer parts.

[rcmaniac25]

I have tried combinations of the following

• Unfocusing application (click away but still visible)
• Backgrounding application (hide behind another window)
• leaving the models selected (when a 3mf is first loaded, all the models are selected)
• unselecting the models
• plater view
• slice view
• leave on bed 1
• changing to the other bed before changing back (has the fun of not always showing that it's slicing, or sometimes just not slicing unless slice view is opened)

The one time it didn't crash it was background + plater view + unselected model + never clicked away from first bed. Same arrangement has not resulted in anything other then crashes.

I'm more wondering if it has to do with wipe into infill, as I know that is only processed during gcode generation phase and when I first made the project, it sliced without issue. But "click on 1-2 things and let slice" is a lot less mental occupation then "uncheck every wipe into infill" option to test if it doesn't crash then.

Until PS maintains multi-color painting when doing cut/merge/split, I can't do a "merge" of all the individual objects without loosing the multi-color painting, otherwise I would merge everything into one object and set the wipe into infill (like the 2nd bed). Otherwise I'd test that as a viable option.

[murk-sy]

Somewhat minimised project.

Bamboo Dragon-minimised-issue13930.zip

When you just slice, it crashes on generating gcode.

Removing a particular part can cause an "access violation" error without closing. Readding the parts again (with undo) will cause "access violation" to appear on the original files as well.

[rcmaniac25]

I've been having issues compiling the project for some reason and it's probably a me thing, else I would make a ticket... but last time I managed to compile it, the debug version would give you the error without closing the application. But with release builds would simply close the application. So you're probably hitting a/the issue, but just with the debug build.

[Jan-Soustruznik]

Hello, @rcmaniac25, thank you for your report. I was able to reproduce your issue. I created an internal issue, no. SPE-2640.