Jump to content
Ultimaker Community of 3D Printing Experts
Sign in to follow this  

Memory: Something went wrong during slicing

Recommended Posts

Everytime i try to slice a bigger model with cura I get this error.

Here's the log:

File C:\Users\Chuleo\Desktop\cellularThing_optimizedForMakerbot.stl is being chain exported.

Carve procedure took 1 minute 29 seconds.

Preface procedure took 1 minute 4 seconds.

Inset procedure took 6 minutes 7 seconds.

Fill procedure took 15 minutes 6 seconds.

Traceback (most recent call last):

File "app_main.py", line 51, in run_toplevel

File "C:\Program Files (x86)\Cura_12.08\Cura\cura.py", line 80, in


File "C:\Program Files (x86)\Cura_12.08\Cura\cura.py", line 72, in main


File "C:\Program Files (x86)\Cura_12.08\Cura\util\sliceRun.py", line 81, in runSlice


File "C:\Program Files (x86)\Cura_12.08\Cura\cura_sf\skeinforge_application\skeinforge_utilities\skeinforge_craft.py", line 135, in writeOutput

return pluginModule.writeOutput(fileName, shouldAnalyze)

File "C:\Program Files (x86)\Cura_12.08\Cura\cura_sf\skeinforge_application\skeinforge_plugins\craft_plugins\export.py", line 275, in writeOutput

gcodeText = skeinforge_craft.getChainTextFromProcedures(fileName, procedures[: -1], gcodeText)

File "C:\Program Files (x86)\Cura_12.08\Cura\cura_sf\skeinforge_application\skeinforge_utilities\skeinforge_craft.py", line 44, in getChainTextFromProcedures

text = craftModule.getCraftedText(fileName, text)

File "C:\Program Files (x86)\Cura_12.08\Cura\cura_sf\skeinforge_application\skeinforge_plugins\craft_plugins\speed.py", line 143, in getCraftedText

return getCraftedTextFromText(archive.getTextIfEmpty(fileName, text), repository)

File "C:\Program Files (x86)\Cura_12.08\Cura\cura_sf\skeinforge_application\skeinforge_plugins\craft_plugins\speed.py", line 153, in getCraftedTextFromText

return SpeedSkein().getCraftedGcode(gcodeText, repository)

File "C:\Program Files (x86)\Cura_12.08\Cura\cura_sf\skeinforge_application\skeinforge_plugins\craft_plugins\speed.py", line 272, in getCraftedGcode


File "C:\Program Files (x86)\Cura_12.08\Cura\cura_sf\skeinforge_application\skeinforge_plugins\craft_plugins\speed.py", line 349, in parseLine


File "C:\Program Files (x86)\Cura_12.08\Cura\cura_sf\fabmetheus_utilities\gcodec.py", line 330, in addLine

self.output.write(line + '\n')


How can I fix that? As a test I sliced the same model with 1mm layer height, which worked just fine.

It can't be because of the amount of RAM (10 of 16GB Free in normal operation.) Nor can't it be because of lack of disk space.

I run Windows 7 x64 (The same thing happens with my desktop computer and my Notebook)

Best Regards


Share this post

Link to post
Share on other sites

The 32 bit pypy implementation can only use 2GB of memory under windows. So even if you have 10GB of free ram, it will still bug out after using 2GB. Which is a bit of a shame, as the slicing process is currently quite memory hungry.

I've never had a model so complex that it would bug out like this, but other people have had the same problem.

However, a memory error could also indicate a problem with your RAM. I highly recommend running memtest:


to be sure that is not it.

(This problem is limited to Windows, Mac is always 64 bit, and for linux there is a 64bit pypy to use)

Share this post

Link to post
Share on other sites

At 0.2mm layers the cellularThing_optimizedForMakerbot.stl seems to slice, but it is using a huge amount of memory, like 800MB. With thinner layers that would get even worse. Slic3r or Kisslicer might do a better job at these models.

It's a known problem, and solving it would mean moving to another slicer (Cura is Skeinforge based), but that's no an easy change to make.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Our picks

    • Ultimaker Cura | a new interface
      We're not only trying to always make Ultimaker Cura better with the usual new features and improvements we build, but we're also trying to make it more pleasant to operate. The interface was the focus for the upcoming release, from which we would already like to present you the first glance. 
        • Like
      • 114 replies
    • "Back To The Future" using Generative Design & Investment Casting
      Designing for light-weight parts is becoming more important, and I’m a firm believer in the need to produce lighter weight, less over-engineered parts for the future. This is for sustainability reasons because we need to be using less raw materials and, in things like transportation, it impacts the energy usage of the product during it’s service life.
        • Like
      • 12 replies

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!