The problem is that by holding the memory you can't do anything but try and clear the bed first and that can be a real challenge with a large print run. I would rather have to slice it again then struggle with a bogged down computer.

Possibly but then, in my mind, it should dump the memory when the print is completed.

@tinken It does to a certain extent, but with a big build it's so incredibly sluggish getting to that option it's faster to kill the program.

@tinken Yes it is, and the machine returns to normal operation.

So some of my frustration with Matterhackers is the lack of timely response on this board. Responded with some detailed screenshots showing the memory drain caused by MatterControl and still await some kind of answer.

Was this what you wanted or do you need more to show what is happening?

@mavin Calibration didn't fix the issue and printing with PETG so no fans at all, I suspect the file now, when I break individual components to print I get the same results.

@tinken thanks, it's kind of a moot point as the project won't fly for other reasons,.

I got them from Thingverse, it's a an enclosure plan for an Ender3 pro. https://www.thingiverse.com/thing:3598219

This is the only part that won't print properly.

Third attempt at printing these pieces, part way the print shifts backwards and I can't see why. Printing PETG, brass 0.4 nozzle at 250 and bed temp of 65 degrees. Running lastest MC in fine mode with default settings.

It seems to be these rollers as other prints are coming out just fine. I have calibrated my Z motors, Z axis and levelled the bed but still to joy. Filament is in a dryer.

I run MC on a stand alone Win 7 laptop with 4GB ram,, when i start MC it runs smooth but when a print completes the memory is ramped up and stays that way, MC is very slow to respond and most times I am required to end the program through Task Manager. Some example pictures, I ran a print overnight and returned to see the screen like this:

The Task manager shows this:

Closing Task Manager shows this:

Restarting MC: (note memory usage at startup).

I am not the first experiencing this, it's been mention constantly on this forum, the program continues to consume memory until it maxes out and does not relinquish it even when prints are done.