Access violation when trying to slice after switching to another preset and back again. #5550
Closed
3 tasks done
Labels
bug
Something isn't working
Is there an existing issue for this problem?
OrcaSlicer Version
2.1.0 Beta
Operating System (OS)
Windows
OS Version
WIndows 10
Additional system information
AMD 3900x
32GB RAM
Printer
Creality CR10 Smart Pro
How to reproduce
Not sure how anyone else can reproduce but I made a 1mm nozzle preset the other day and today I switched to it and back to my usual 0.4. Then I went to slice and got the error.
I can no longer slice with any of my profiles without this error.
Actual results
Exception as outlined in the screenshot
Expected results
Slicing works.
Project file & Debug log uploads
AccessViolationProject.zip
log.zip
Checklist of files to include
Anything else?
I upgraded to 2.1.0-beta to see if it'd fix the issue but the same problem happened.
Now I cannot slice with any of my profiles at all.
One thing of NOTE is that I have built Orca Slicer myself and ran the build too in order to do make some changes. When I switch between running the official release and my development build, Orca always redownloads the Bambu Network plugin. That's fine, I can handle that but I have also noticed that more often than not when I first go back to running Orca release, my user presets don't load. I then quit Orca, start it again and they are there.
I have attached my log files from today. Not all saw this issue but I'm not sure which one it started on.
I loaded up my 2.1.0 alpha project and the same issue happens. Here's the callstack.
`
`
Here is the code
// boundary conditions
if(m_left == spline::second_deriv) {
// 2*c[0] = f''
A(0,0)=2.0;
A(0,1)=0.0;
rhs[0]=m_left_value;
} else if(m_left == spline::first_deriv) {
// b[0] = f', needs to be re-expressed in terms of c:
`
And the exception is on the line A(0,0) = 2.0;
Going back to my project and looking at the small area fill compensation settings (The setting was unchecked in my profile but I checked it to see what the configuration looked like) I see this corruption.
After restoring the configuration for the SAFC from another preset, I can slice again. It's strange that it got corrupted but also strange that it was even trying to process that when the setting of off.
The text was updated successfully, but these errors were encountered: