Slic3r settings crashing my machine

[karla-lopez 0]

I've been testing using Slic3r version 0.9.10b to print on Ultimaker.

 

It was working almost as good as when using Cura, but I was getting some misplaced layers, like the printer was missing some steps, and I read in some forums it could be the slicing settings. I made a couple of changes, it got way better in my test robot, but I now have a problem when I use Slic3r with the new settings on Debian servers to slice a file.

 

When I use the adjusted settings, Slic3r hangs on 32-bit system and causes a heap (memory) error on 64-bit. In both cases it either does not complete or eventually crashes completely. In either case it heavily utilizes CPU >98%.

It means my new settings cause problems for Slic3r, right?

I would like to find out which settings are causing the crash but not sure how to start looking for it.

Any help/tip is welcome!

 

[illuminarti 18]

In the printer settings -> advanced, try setting the resolution to a non-zero value. I generally use 0.05, assuming my layer height is at least twice that. That helps it to simplify the mesh to make the slicing task more manageable.

Also, you should read http://www.extrudable.me/2013/11/03/slic3r-strange-defaults-causing-qu-bd-woes/, and consider setting all of the extrusion width settings to equal your nozzle width (0.4mm, usually).

 

[Daid 304]

Slic3r hangs on 32-bit system and causes a heap (memory) error on 64-bit. In both cases it either does not complete or eventually crashes completely. In either case it heavily utilizes CPU >98%.

 

Last time I tried Slic3r, I had the same issue, people told me that you had to disable the "multithreaded" support, as it was causing crashes. Not sure if that is still the case, as this was half a year ago.

(Funny fact, Cura is still faster, and still single threaded)

 

[karla-lopez 0]

Thank you illuminarti and Daid! I will your suggestions and come back to tell what happened

Thanks,

Karla