The diskspace management problem persists in v53.2.2. Unfortunately there is no transparency to how much space might be consumed or where the temporary files are stored. I've found some of them on my mac and with about 2500 images, I'm seeing a minimum of 30M per 10 iterations (but "About this mac" seems to indicate a lot more, like maybe 3-4x as much consumption, i.e., 100M per 10 iterations). It's understandable why the disk consumption could be so high, but the fact that there's no ability to estimate it ahead of time is a major headache for large models with many iterations.