jimc wrote:ok so i have been looking into this a bit and did some tests. i have kept the memory monitor running on my desktop of my mac while s3d has been running for the past couple days. i loaded stl after stl. mostly large ones. i would go ahead and slice them then remove the model and load another. i did watch the memory usage creep up with each model and go from 58mb all the way up to 4gb after the final stl i loaded which had 2 mil polygons. for me to get it to 4gb i probably loaded and sliced 15 different med to large models. after the final one i removed the model and it dropped right back down to 700mb. basically it is doing what it think it should with no type of error or bug there. it will build to a certain point or until you remove the model and then it drops back down. this would seem normal to me.
58mb start to 700mb after removed model is normal? Where are the 642MB? Just load it up with instruments and find out. Not too hard to track memory leaks. If it isn't leaked memory and there is something else holding on to it you can find that too and release the memory.