180mm x 180mm x 200mm 99.1MB GCode File Won't Load

[RenaeMacLeod]

I am printing the following file...

http://www.thingiverse.com/thing:6397

... scaled to 200 in Slic3r 0.99. When I attempt to load it I press the 'Load file' button, select the file, then press the 'Open' button. After waiting about 20 minutes there is no change to anything. If I press 'Load file' again it presents the 'Open' dialog as if it's waiting to load a file.

It did take a number of hours to slice so I understand it is a complex print. This may be a feature request to increase the file size limit, or it could be an issue in that there is no file size limit listed or there is no restriction on size and this file is simply not loading.

[RenaeMacLeod]

The same file at 150% also didn't load. If I click 'Load file' about 30 seconds after trying to load the file I get an error. I just tried reproducing the error and I was unsuccessful. I did load a file that did print previously and it loaded fine.

[iXce]

Hm, interesting. I'd bet we are running out of memory here. Is there any error reported ? How much RAM does your computer have ?

[iXce]

I just successfully loaded a 141M large gcode file (a 200%, 0.12mm layer height, 0.1 infill slice of this model), so there's no limit in Pronterface. However, if you are using the Windows binaries, they are using 32 bit libraries, which will limit Pronterface's memory usage to 3 or 4 gigs, while after loading this 141M file Pronterface was taking 6 gigs (this probably has to be investigated, but Python objects introduce large overheads).

[RenaeMacLeod]

No error is reported. I left it for about 30 minutes total after pressing the open button, maybe more. I only get an error dialog if I press the 'Load file' button while it is presumably attempting to load the file. I am running the Python files on Windows, not the binary built by kliment.

My computer a top end Lenovo X61T (1.8 GHz, 8GB, Windows 8 x64) and printing is the only thing this computer does. I do the slicing and anything else 3D printing related on another much more powerful computer.

A 20MB 100% file of the same object loaded after a number of minutes, I didn't time it. One thing I also noted was that in Slic3r I had it set to not cross perimeters and turning that off for the 200% size resulted in a 30MB file which also loaded after about 3 minutes.

Do you want me to put the GCode files online for you to test?

[iXce]

If you want, but I really fear this is just that the file is exploding the
3 or 4GB ram limit.

2013/6/1 RenaeMacLeod notifications@github.com

No error is reported. I left it for about 30 minutes total after pressing
the open button, maybe more. I only get an error dialog if I press the
'Load file' button while it is presumably attempting to load the file. I am
running the Python files on Windows, not the binary built by someone
another person as that binary doesn't seem to be very recent.

My computer a top end Lenovo X61T (1.8 GHz, 8GB, Windows 8 x64) and
printing is the only thing this computer does. I do the slicing and
anything else 3D printing related on another much more powerful computer.

A 20MB 100% file of the same object loaded after a number of minutes, I
didn't time it. One thing I also noted was that in Slic3r I had it set to
not cross perimeters and turning that off for the 200% size resulted in a
30MB file which also loaded after about 3 minutes.

Do you want me to put the GCode files online for you to test?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/380#issuecomment-18791812
.

[iXce]

I've reduced Gcoder's memory footprint by 50% or so using a Cython-based Line class (which is much more compact than using Python objects). We'll try to include it in the next binary round. (Slic3r has been slicing your test object for 2+ hours now on my computer, so I couldn't test with it, but I'm confident it'll be much lighter)

[iXce]

Obviously it ended 2 minutes later. The 21MB file is using ~130MB of RAM once parsed, so the factor has been reduced to a factor 6 or so, instead of 20+.

[iXce]

After another pass of optimization memory usage has been further trimmed down. With other things loaded (libraries and stuff), my memory auditor claims we are using about 84MB + the 21MB of the file, and the total writable memory is 164MB. We'll release new binaries soonish with these improvements.

[RenaeMacLeod]

Thanks! I'll grab the experimental branch and test it in the next few days.

[iXce]

Hey, any news ? Kliment also made new binaries which should include these improvements, for what it's worth !

[iXce]

Fairly sure this is fixed :) Closing, please reopen if it still won't load !

-- iXce, the garbage collector

[billy0329]

hi iXCE,
I have a related issue regarding memory error.
I have sent a message with the details of the problem to your email.
I hope you consider if you have time.
Thank you in advance.