-
-
Notifications
You must be signed in to change notification settings - Fork 833
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashing/Closing While Slicing Complex or A lot of Layers #2921
Comments
strangely i have this issue in bambu slicer and orca, but not nearly as often in orca slicer. I also wonder if it's something to do with the e-cores / p-cores on these cpus. I have z790 and 14900k cpu. |
@silence48 what ram do you have? I have had issues with both bambu and orca. I also have the 13900K(similar) and z790. |
TeamGroup T-Create Expert 48GB Kit (2 x 24GB) DDR5-7200 PC5-57600 CL34 Dual Channel Desktop Memory Kit CTCWD548G7200HC34ADC01 It's not overclocked because the pc didn't run stable at 7200 mhz. I am running the ram at 5600 mt/s This issue has a possible relationship to 3279 Screen Recording of failure.
Another log:
TLDR; It could be memory related, it could be related to threading and sometimes there's issues where stuff needs to be numa aware to properly utilize e-cores, but i'm thinking that's unrelated due to the fact i parked the e-cores and it still crashed. |
There is a likely relationship to 3375 |
Another relationship to 3157 |
I upgraded my PC to DDR5 6800 and a new Motherboard. Still same issue. Same issue even after disabling e cores. @silence48 You're solution has solved it on my end. I wonder what the issue stems from. |
@silence48 You are right, atleast on my end all crashes has stopped soon as i change affinity in my task manager to only the P cores( 0-7 for 8 P core cpu). I don't think parking cores solves this. Parked cores can still be activated when needed, you either need to fully disable them or only set affinity to cores 0-7. I have not tried compatibility mode. @Zechs2205 i don't now why that wouldn't work for you, i have exactly same setup except for ram i run slightly slower and Gskills. Doing the above helped me getting reliable slices off. I really feel like this is an E core issue since i've had this issue with every slicer i've tried so far and they all crash soon as i hit slice button. Doing the above solved for all of the slicers i tried(Cura, Creality Print and OrcaSlicer) |
I figured it out. It's not E core its Hyperthreading. I used project lasso to test different hypothesis. I found that hyperthreading is casing problems with many different applications. I don't know why still but it seems to be a problem on the LGA1700 bc my previous I9 10th didnt have any of those issues. |
Orca bot: this issue is stale because it has been open for 90 days with no activity. |
Orca bot: This issue was closed because it has been inactive for 7 days since being marked as stale. |
OrcaSlicer Version
1.8.0
OS version
Windows 11
Additional system information
Printer
Bambu Lab P1P
How to reproduce
Actual results
Orca slicer just crashes/closes
Expected results
Normal Slicing
Project file & Debug log uploads
debug_network_Wed_Nov_29_04_46_31.log
crash_Sat_Nov_25_01_55_07_0.log
crash_Sat_Nov_25_01_55_26_0.log
Checklist of files to include
The text was updated successfully, but these errors were encountered: