Crash to desktop when slicing certain models.

[jcford73]

OrcaSlicer Version

1.8.0-rc2

OS version

Windows 11 Pro

Additional system information

CPU: Intel Core i9 13900k RAM: 64GB DDR5 GPU: GeForce RTX 4090

Printer

Sovol SV06

How to reproduce

Simply attempt to slice the model

Actual results

Slicing certain models such as this grim reaper figure cause the program to crash to desktop with no error message. This happens in PrusaSlicer 2.6.1 as well. Likely affects the whole slic3r family.

I ran OrcaSlicer and PrusaSlicer in Ubuntu in a VirtualBox VM and that version was able to slice the models, if slowly.

Today, I tried turning on Windows 8 compatibility mode for OrcaSlicer in Windows 11. To my surprise, it didn't crash this time. It took a very long time to slice the models, but it worked. So I have a workaround.

Feedback on Reddit indicated others have this problem with certain models in the Windows version of the software. Hopefully this Windows 8 compatibility clue will help diagnose the cause.

Expected results

Successful slicing

Project file & Debug log uploads

crash_Thu_Nov_16_14_25_33_0.zip ReaperCloak_Main.zip

Checklist of files to include

• [X] Log file
• [X] Project file

[Noisyfox]

Could you try this build https://github.com/SoftFever/OrcaSlicer/actions/runs/6897958644 and upload the new crash log? We've improved the crash log a little bit and would like to see how effective it is. Thanks.

[jcford73]

I tried that build. It does still crash, but it does not generate a crash log file at all. Here's the debug log file it generates, though. debug_Fri_Nov_17_13_51_24_18564.log.zip

[silence48]

Another c0000005 ACCESS_VIOLATION Related issues include #2921 #3375 #3340 #3292 #3157 #2896 #2888

[jcford73]

Any news on these crashes? 1.9.1 on Windows is still crashing on a lot of models. Sometimes regardless of settings, sometimes only when trying to generate tree supports. Always the same CTD behavior.

[HellBz]

Same Problem, but my Slicer simply closing, without Crash-Log.

debug_Tue_Mar_12_20_39_00_26352.log

[HellBz]

What i can find out, only for Klipper based Printers, the Slicer Crash, if i Slice the Same file for my Tronxy X5Sa based on Marlin, all works fine.

if i switch back to my K1-Max Profile, the Slicer instantly crash on large Files.

But the Same happen on PrusaSlicer

[jcford73]

In case it helps debug this issue, I've found if I set process priority to realtime and the processor affinity to only use the first half-dozen or so cores, it will slice. It will just take a really long time. This is probably similar to what is happening when I was turning on Windows 8 compatibility mode.

edit: tried again with just the processor affinity since I was fairly certain the process priority wasn't doing anything. I was correct. It worked with just the affinity setting. So maybe the software is having some sort of problem with these later Intel CPUs? This is a Core I9 13900k.

[Noisyfox]

Is there any crash log available?

[jcford73]

Here's the most recent using OrcaSlicer 2.0 beta. And here's the system specs again just for reference.

OS version Windows 11 Pro

Additional system information CPU: Intel Core i9 13900k RAM: 64GB DDR5 GPU: GeForce RTX 4090

debug_Tue_Mar_19_22_20_28_23524.log.zip

[github-actions[bot]]

Orca bot: this issue is stale because it has been open for 90 days with no activity.

[jcford73]

This issue should not close. It's definitely still happening. I have to set processor affinity to limit the number of cores in use by the software or it will crash when slicing any but the simplest of models.