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

SuperSlicer Locks up, CPU goes to 100% #2664

Closed
notching opened this issue Apr 8, 2022 · 4 comments
Closed

SuperSlicer Locks up, CPU goes to 100% #2664

notching opened this issue Apr 8, 2022 · 4 comments
Labels
fix is live in the last release Please download /build the last release and try to reproduce. problem

Comments

@notching
Copy link

notching commented Apr 8, 2022

Version

2.3.57.11

Operating system type + version

Windows 10

Behavior

Superslicer locks up when trying to slice, CPU goes to 100%.

SpringFlat_Soft_v3.3.3mf.zip

@supermerill supermerill added bug Something isn't working as intended problem and removed bug Something isn't working as intended labels Apr 8, 2022
@supermerill
Copy link
Owner

It's not really stuck, it just takes a very very long time.
The problem lie in the shape & the algo for gapfill. The shape makes hte current algo to be on its worst-case scenario, and the spiral creates a very high amount of points/paths.

One simple solution is to revert the resolution field to its default value of 0.0125 to prevent the humongous amount of points to stall the slicing.

@notching
Copy link
Author

notching commented Apr 8, 2022 via email

@supermerill
Copy link
Owner

The cancel is check before & after that step, as it should be computed quickly.

@supermerill
Copy link
Owner

I added some failsafe to decrease the resolution if the gapfill is detected with too may points.

What a huge gapfill btw.
image

@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 Apr 8, 2022
@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 Jul 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix is live in the last release Please download /build the last release and try to reproduce. problem
Projects
None yet
Development

No branches or pull requests

2 participants