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

std::bad_alloc on linux with "keep only bridges" #511

Closed
khumarahn opened this issue Sep 30, 2020 · 4 comments
Closed

std::bad_alloc on linux with "keep only bridges" #511

khumarahn opened this issue Sep 30, 2020 · 4 comments
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

@khumarahn
Copy link

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

@khumarahn
Copy link
Author

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.

@supermerill supermerill added the bug Something isn't working as intended label Sep 30, 2020
@supermerill
Copy link
Owner

it's the 2.2.53.2 ?

@khumarahn
Copy link
Author

yes!

@supermerill supermerill added the fixed for the next version That means that you should be able to test it in the latest nightly build label Oct 1, 2020
@supermerill supermerill added fix is live in the last release Please download /build the last release and try to reproduce. and removed fixed for the next version That means that you should be able to test it in the latest nightly build labels Oct 5, 2020
@khumarahn
Copy link
Author

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.
Projects
None yet
Development

No branches or pull requests

2 participants