Slicing large models with current head consumes all available memory #1044

Closed
festlv opened this Issue Mar 11, 2013 · 6 comments

Comments

Projects
None yet
3 participants
@festlv

festlv commented Mar 11, 2013

Problem: slicing a plate full of parts (for Prusa Mendel2, exactly this model: http://faili.wot.lv/0/p1.stl) consumes all available memory (8GB RAM + 3GB swap, mostly free before slicing) and is killed by OS:

$ dmesg
..
[66492.036372] Out of memory: Kill process 7800 (perl) score 886 or sacrifice child
..

This happens on current head: 964accb

This does not happen on 0.9.8 (09bdd2e).

Slicing smaller models succeeds and the results are good, but it really takes longer with HEAD Slic3r than with 0.9.8.

Please let me know if you need more info on reproducing this issue- I'm glad to help.

@festlv

This comment has been minimized.

Show comment Hide comment
@festlv

festlv Mar 11, 2013

After some more tests, this only is happening when "Avoid crossing perimeters" is on- without changing any other settings, and on the same stl.

festlv commented Mar 11, 2013

After some more tests, this only is happening when "Avoid crossing perimeters" is on- without changing any other settings, and on the same stl.

@alexrj

This comment has been minimized.

Show comment Hide comment
@alexrj

alexrj Mar 11, 2013

Member

Can you attach your config.ini please?

Member

alexrj commented Mar 11, 2013

Can you attach your config.ini please?

@festlv

This comment has been minimized.

Show comment Hide comment
@festlv

festlv Mar 11, 2013

Here's the config which has this problem: http://faili.wot.lv/tmp/config-unusable.ini
Here's a screenshot from htop: http://faili.wot.lv/tmp/2013-03-11_14-53-59.jpg

Extreme memory consumption starts at the point wher Slic3r says it's "Exporting G-code" until that point, everything seems normal.

Perl version, in case it's relevant:

? ~ perl -v
This is perl 5, version 16, subversion 2 (v5.16.2) built for x86_64-linux-thread-multi

festlv commented Mar 11, 2013

Here's the config which has this problem: http://faili.wot.lv/tmp/config-unusable.ini
Here's a screenshot from htop: http://faili.wot.lv/tmp/2013-03-11_14-53-59.jpg

Extreme memory consumption starts at the point wher Slic3r says it's "Exporting G-code" until that point, everything seems normal.

Perl version, in case it's relevant:

? ~ perl -v
This is perl 5, version 16, subversion 2 (v5.16.2) built for x86_64-linux-thread-multi

@JohK

This comment has been minimized.

Show comment Hide comment
@JohK

JohK Mar 12, 2013

I have seen similar behaviour with "avoid crossing perimeters" on models that have islands connected by only thin walls. Additionally this sometimes leads to weird fast travel moves away from the current printing position to a spot and away from that spot to the new printing position. (Sorry I can't post the particular model, I have to see if I can reproduce it with another model).
Maybe related to #979 ?

JohK commented Mar 12, 2013

I have seen similar behaviour with "avoid crossing perimeters" on models that have islands connected by only thin walls. Additionally this sometimes leads to weird fast travel moves away from the current printing position to a spot and away from that spot to the new printing position. (Sorry I can't post the particular model, I have to see if I can reproduce it with another model).
Maybe related to #979 ?

@alexrj

This comment has been minimized.

Show comment Hide comment
@alexrj

alexrj Mar 19, 2013

Member

@festiv, I'm testing your p1.stl and I confirm there's a problem of efficiency of avoid-crossing-perimetes with many islands.

Member

alexrj commented Mar 19, 2013

@festiv, I'm testing your p1.stl and I confirm there's a problem of efficiency of avoid-crossing-perimetes with many islands.

@alexrj

This comment has been minimized.

Show comment Hide comment
@alexrj

alexrj Mar 19, 2013

Member

It was a genuine memory leak. Now fixed. Thank you!

Member

alexrj commented Mar 19, 2013

It was a genuine memory leak. Now fixed. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment