-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Windows 10 machine locks up while generating supports #142
Comments
I have never seen something like this. It allocated 30GB of RAM on my computer, then the screen started to flicker :-) |
bubnikv
added a commit
that referenced
this issue
Feb 19, 2017
Thanks, it is an infinite loop due to numerical rounding effects. |
Well that was fast. Thank you! |
Yeah, it is a new code, there are dragons. I am trying to stabilize Slic3r for the final release to our customers. So I am thankful to you for the bug report. |
wavexx
pushed a commit
to wavexx/PrusaSlicer
that referenced
this issue
Sep 21, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
Version 1.33.6-prusa3d-win64
Operating system type + version
Windows 10 Home Edition, 64 bit, current patchlevel
Behavior
I load the STL file from http://www.thingiverse.com/thing:1930525 (attached) and increase the number of copies to 3 total. I leave orientation and placement of the models as is.
I configure the support settings as shown in the screenshot.
As I have background processing disabled, I click on the "Slice now" button.
CPU usage rises to 100% (as is to be expected). A short while after the progress bar hits the "Generating support" phase, the whole computer locks up. The images freezes, the mouse cannot be moved, the Task Manager cannot be opened. I had to reset my machine.
The same settings with version 1.31.6-prusa3d-win64 result in a completed calculation and G-Code generation
STL/Config (.ZIP) where problem occurs
Prusa_IGES_Drylin_adaptor.zip
Slic3r_config_bundle.zip
The text was updated successfully, but these errors were encountered: