forked from prusa3d/PrusaSlicer
-
-
Notifications
You must be signed in to change notification settings - Fork 527
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
std::bad_alloc on linux with "keep only bridges" #511
Labels
bug
Something isn't working as intended
fix is live in the last release
Please download /build the last release and try to reproduce.
Comments
A small update: I could reproduce it in windows, the message was "bad array new length". But when I moved the part on the table slightly, the error disappeared. |
it's the 2.2.53.2 ? |
yes! |
supermerill
added a commit
that referenced
this issue
Oct 1, 2020
supermerill
added a commit
that referenced
this issue
Oct 1, 2020
I could not reproduce it with 2.53.3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working as intended
fix is live in the last release
Please download /build the last release and try to reproduce.
Hi, I run superslicer-2.2.53 appimage.
I have a part which refuses to slice (though I successfully sliced many other things), giving me a "std::bad_alloc" error. Trying to find out what caused it, I noticed that if I change "Keep only bridges" to "Disabled" (in "No perimeters in bridge area" setting), then it slices well.
I observe the same behavior in arch linux and linux mint, but I could not reproduce the error in windows 10. To reproduce in in linux, I set up a basic profile (e.g. prusa mini) and do not change any settings except "Keep only bridges".
cannot-slice.3mf.txt
The text was updated successfully, but these errors were encountered: