OrcaSlicer
OrcaSlicer copied to clipboard
SoftFever
Consistent crash
OrcaSlicer Version
1.9.0 Beta1
OS version
Windows 11 23H2 build 22631,2861
Additional system information
13900k (non-oc), RTX Strix 4090 OC, 64GB (4*16gb) Corsair dominator Titanium at 4533Mhz (XMP won't boot)
Reguraly with both OrcaSlicer & BambuStudio i get an STL i can consistently try to slice and make the slicer crash. If i try too much it sometimes takes the whole system with it (with BSOD's like Clock Watchdog Timeout). No matter what settings i try to change, doesn't help. Currently experiencing with with the "AMS Pro 1.00-full-set-petg.3mf" file from Humebeam @ printables.com. The same applies to BambuSlicer so it's something that's shared between them, but OC is my preferred slicer due to more control settings so i figured i'd report here.
There is a workaround which is to rightclick the desktop shortcut and set it to run in Windows 8 compatibility mode. It's slower to slice, but in that mode i've yet to experience a crash. Attached are the logs for just a few of the slice tries
Printer
Bambulab X1C
How to reproduce
- Load 3mf file
- slice
- Crash
Actual results
Full system crash bsod depending on the circumstances
Expected results
succesful slice in non-windows 8 compatibility mode
Project file & Debug log uploads
log.zip hydra-pro-1.00-full-set-petg.zip
Checklist of files to include
- [X] Log file
- [X] Project file
** edit ** Not even Compatibility mode is safe with this file it seems
Very possible, I do remember seeing that ACCESS VIOLATION bsod a few times too, and the hydra ams parts do have a lot of layers (at .2mm layer height). If there's anything I can further provide to help fix, I just need to know what.
Very possible, I do remember seeing that ACCESS VIOLATION bsod a few times too, and the hydra ams parts do have a lot of layers (at .2mm layer height). If there's anything I can further provide to help fix, I just need to know what.
Thank you for your insight. I just actually found this project, in fact because of this bug (the bug also exists in bambu slicer) And so I would rather contribute to this than a for profit company, so here I am 😆
I will definitely report back if I find a solution or can enact one in the code.
Very possible, I do remember seeing that ACCESS VIOLATION bsod a few times too, and the hydra ams parts do have a lot of layers (at .2mm layer height). If there's anything I can further provide to help fix, I just need to know what.
can you run a test and enable compatibility mode for windows 8 and then try again? For me this caused it to no longer crash, and instead it is froze up but it says it's using 3% of my cpu and over 8gb of memory currently. I'm gonna let it sit for a while to see if anything interesting pops out my logs.
It just now finished slicing the file.
Try to enable windows compatibility mode (for windows 8) And maybe it'll help you like it helped me!
Hey everyone,
Just a heads-up - OrcaSlicer tends to crash if we switch to the device page too soon, before our printer's connected. Good news, though – I've got a fix lined up for the next update. For now, just hang on for about 10-30 seconds after firing up OrcaSlicer before you switch to the device page.
Also, if anyone's game, I'd really appreciate some help testing this fix. The latest build will be ready in about an hour. You can download it [here] and let me know if you run into any more crashes. Thanks a ton!
@silence48 as mentioned at the bottom of the OP 8 already am. Even CM mode isn't 'safe' from the crashes.
@SoftFever
For now, just hang on for about 10-30 seconds after firing up OrcaSlicer before you switch to the device page.
I don't see how that's going to assist, as my OS doesn't switch to device tab at all and my crashes were during slicing, generating gcode, uploading to printer. I never hit 'send and print'. I only use 'send', and launch a print from the X1C screen.
In bed now, will try the new build tomorrow
@SoftFever As expected, this recent build did NOT fix the crashes during slicing. Still crashes during slicing (always on plate 2 of this 3md file) before you even get to send the sliced to the printer. So it's definitely not an issue related to switching to the device tab too soon. For that the file needs to have been sent to the printer. In my case that hasn't even happened yet. Updated log using tonights build. log.zip
And i just had it crash (in compatibility mode) trying to slice 4 simple PTFE buttons for the AMS. Crashes when trying to use 5 bottom & top layers. PTFE load buttons.zip
edit And crashes again after succesful slice, when trying to send to printer edit2 and now it crashes trying to slice again after slight increasing distance between them, changing wall count from 2 to 3 and top/bottom layers from 4 to 3 (in non-compat mode)
Loading that same 3mf file in the latest bambu studio slices and sends to printer just fine.
It's a regression bug cause by PR https://github.com/SoftFever/OrcaSlicer/pull/3014
What i have noticed running the latest build is that the crashes with those PTFE buttons sometimes do slices, but it fails to send. When hitting send it goes right for about the first 10% and when it should actually start uploading, OS crashes even in compat mode. Reverting to 1.8.1 fixed the upload issue but it doesn't fix the slicing crashes.
Can you try this build? https://github.com/SoftFever/OrcaSlicer/actions/runs/7377220740
Certainly, if you can tell me how to download the windows EXE from it :)
Sure, you can download it here: https://github.com/SoftFever/OrcaSlicer/actions/runs/7377220740
Still crashes the moment i try to slice plate2 of the initial 3mf i posted (hydra pro AMS)
Running in compat mode crashes at 80% (generating gcode) of plate 2, and obviously is a lot slower. log.zip. That said, don't spend new years day on this, i'm alone so i got nothin better to do, spend it with your family ;)
@SoftFever I see there's been an official 1.9.0 release. I don't suppose it this issue does it?
Edit Nope. Still crashes, even on something as simple as https://www.thingiverse.com/thing:5240529
Project file & logs attached.
@SoftFever I see there's been an official 1.9.0 release. I don't suppose it this issue does it?
Edit Nope. Still crashes, even on something as simple as https://www.thingiverse.com/thing:5240529
Project file & logs attached.
I have tried all the projects you attached, but I can't reproduce the crashing issue. Your case seems different from any other reports. There might be some conflicting environment settings in your OS. I have no clues at the moment.
If you wanna do a TeamViewer session and have a look around, that certainly can be arranged. BS seems to work for the moment.
Have you guys tried changing the affinity of the process. I have crashes in every slicer on my main rig which contains a i9 13900k. Soon as i set the affinity to only core 0-7(The first cores are P cores so simple to reproduce) all crashes have been stopped in every slicer i tried so far. I have a i7 11700k and on that machine no crashes since it does not have the new hybrid tech from intel.
Then it's certainly worth a try after work this evening. Thanks for the tip. Will report back
@SoftFever User @chuckie1992 may be on to something. I just succesfully sliced the original attached project file. A bambu Tidy project with 28 different buildplates, and Fibo spool holder project with 6 plates (1 more than the project in this discussion). They may be on to something. Even with my 13900k, cpu usage spiked upwzrds of 40% and depending on the plate into the lower 50's but they didn't crash.
@chuckie1992 i didn't have 0-7 as you mentioned, but i did have 0-4 as the screenshot. They seem to do the trick, i'll keep monitoring this over the next few weeks.
The big projects did lack the ability to make a timelapse though?
@SoftFever User @chuckie1992 may be on to something. I just succesfully sliced the original attached project file. A bambu Tidy project with 28 different buildplates, and Fibo spool holder project with 6 plates (1 more than the project in this discussion). They may be on to something. Even with my 13900k, cpu usage spiked upwzrds of 40% and depending on the plate into the lower 50's but they didn't crash.
@chuckie1992 i didn't have 0-7 as you mentioned, but i did have 0-4 as the screenshot. They seem to do the trick, i'll keep monitoring this over the next few weeks.
Yea this is 100% the reason Slicers like OrcaSlicer crash. They are not programmed to support E cores. You also should have 8 cores with your 13900k, just scroll down in the Affinity list. You also should be able to select core 0 to core 15 due to Hyper Threading technology on intel cpu's. The first 15 cores are P cores and its threads. I just tested with the 1st 8 cores and it stopped crashing. But this also depends on the cpu. Think the i5 version has 6 cores so only the first 12 cores can be used in the Affinity list. It should be a solid workaround for now so people can slice again on their high end machines.
Update: Can confirm that using all 8 P cores and its threads on a i9 13900K works, just tested it with a simple adjustable spool holder which would crash if i use all P and E cores.
@chuckie1992 I got 32 cores (0-31). It is a lot faster with 0-15.
Now just need to find a way to set process affinity permanently, cause it seems to lose that configuration once the application is closed. Doing it the shortcut way as described here https://answers.microsoft.com/en-us/windows/forum/all/how-to-permanently-set-priority-affinity-with/4e83fd39-34a7-49fe-a54a-ee891c38b737 doesn't work. IT launches a command window where you still manually need to enter "orca-slicer.exe"
@SoftFever Could you make this a feature please? To restrict OrcaSlicer to P cores only?
@chuckie1992 I got 32 cores (0-31). It is a lot faster with 0-15.
Now just need to find a way to set process affinity permanently, cause it seems to lose that configuration once the application is closed. Doing it the shortcut way as described here https://answers.microsoft.com/en-us/windows/forum/all/how-to-permanently-set-priority-affinity-with/4e83fd39-34a7-49fe-a54a-ee891c38b737 doesn't work. IT launches a command window where you still manually need to enter "orca-slicer.exe"
@SoftFever Could you make this a feature please? To restrict OrcaSlicer to P cores only?
Yes an app called process lasso: https://bitsum.com/ With that you do the same as in Task manager but the Affinity stays after reboot they claim. And they have a feature to disable Efficiency mode so nothing will run on E cores. But i would just set affinity manually.
And i got 32 cores too 8P cores+ 8 Threads=16+16 E cores= 32 cores 0-15 are P cores/P core threads 16-31 are E cores(no hyperthreading on those so only single thread per core)
@SoftFever Just have to find what exactly in his code doesn't run well under E cores and try to solve it. It should be able to use those cores too to improve overall performance in the app.
You also could try this article, Similar to what Microsoft explains but uses Hexadecimals https://www.windowsdigitals.com/how-to-set-process-cpu-affinity-priority-permanently-in-windows-10/ Windows 10/11 are basically the same. From what i've heard basically GUI refresh and changes to Scheduler to support the new intel hybrid cpu's. But easiest route would be Process Lasso. Free version should do everything you need it to do.