bot wrote:Are you running windows 8 on a machine with less than 4GB of memory? And trying to do 3d work?
That must be fun. I don't think there are any "memory leaks." I think those are "memory allocations." I'm not a software developer, so I don't know for sure... but this does not seem out of line for a piece of software to use. I've had a sliced model where just the VISUALIZATION in memory exceeded 1GB.
It is most certainly a leak.
If you Prepare to Print followed immediately by Exit Preview Mode, with each iteration the memory usage grows. Since there is no way to access "previous" Preparations--i.e. there is no undo, and no history to select a previous g-code, etc.--that is the very definition of a memory leak. The only way this would be expected behavior is if there is a reason
for the memory to grow--for instance, saving the history, either to allow for Undo actions or to allow access to a previously processed file that was not saved to disk