Skip to content
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

Access Violation Error in PrusaSlicer 2.6.0 Alpha 2 #9489

Closed
2 tasks done
jdemacek opened this issue Feb 1, 2023 · 3 comments
Closed
2 tasks done

Access Violation Error in PrusaSlicer 2.6.0 Alpha 2 #9489

jdemacek opened this issue Feb 1, 2023 · 3 comments

Comments

@jdemacek
Copy link

jdemacek commented Feb 1, 2023

Description of the bug

When slicing a complex model with Multi Color parts, I receive an access violation error. No other data given other than a recommendation to restart. I an including a screenshot as well as my project file.

Project File

Screenshot

Project file & How to reproduce

Load linked file and "slice"

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

PrusaSlicer 2.6.0 Alpha 2

Operating system

Windows 11 64 bit

Printer model

Prusa MK3S / MMU2S

@lukasmatena
Copy link
Collaborator

Thanks, reproduced. I simplified the project to run faster in debug mode:
Nazgul_edited.zip

This simplified 3MF asserts during elephant foot compensation and crashes during support spots generation. Which of these issues is the one happening in the original 3MF (if any) I don't know.

@mcclure3dprints
Copy link

What if neither elephant foot compensation or supports are turned on, and I still receive this error code? I have a TPU part and ABS part which fit together. Is there a solution to work around this at the time being?

@kubispe1
Copy link
Collaborator

kubispe1 commented Feb 3, 2023

Ok, we fixed it and tested it. In the next release, Access Violation Error should not appear and slicing would be fine.
Closing, Thanks
image

@kubispe1 kubispe1 closed this as completed Feb 3, 2023
bubnikv pushed a commit that referenced this issue Feb 3, 2023
…s applied

\#9513 \#9489 Fix crash when brim is used - the expansion of very small drops may result in empty polygon, which the support spot generator did not reflect
Fix crashes of stability alert checker, when empty print object was passed to it
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants