MatterControl 2.21.12 (December, 1, 2021)

  • 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:0_1638383992446_B - Print completed overnight_LI (2).jpg

    The Task manager shows this:
    0_1638384012094_C - Task manager MC Open.png

    Closing Task Manager shows this:
    0_1638384043472_D - MC Closed Resources returning.png

    Restarting MC: (note memory usage at startup).
    0_1638384083863_E - MC Restarted.png

    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.

  • 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?

  • Global Moderator

    Is the memory released when you close Mattercontrol?

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

  • Global Moderator

    @pverdin If you press the "Clear Bed" option, see if this releases the memory.

  • @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.

  • Global Moderator

    @pverdin I was asking because I think MC is storing it in ram so that it can access it faster during it's calculations.

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

  • Global Moderator

    @pverdin It should dump when you clear the bed. But it should stay there while it is still on the bed in case you want to modify it or reprint it.

    If it is sliced and you want to modify it again or even move its position, you can drag a primitive over to it. Just delete the primitive. I do this when I am printing on Garolite, so that I can use different areas of the bed each cycle.

  • 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.

  • This version created a really bizarre slice for the top layer of a large ring shape. It printed one short line, then moved over to the other side and printed another one and back and forth, retracting and moving and wasting a lot of time in the process.

    The other solid layers (the bottom and all but the top) printed in about 4 minutes each, the top took more than ten and made a mess of it. I'd submit a trouble ticket but don't see any way to do that, so it looks like complaining here is the way to go.

Log in to reply

Looks like your connection to MatterHackers Community was lost, please wait while we try to reconnect.