A question about virtual memory
Posted: March 10th, 2020, 7:55 am
When I complete a procesing tree to my satifaction (momentary) and save the workspace script, I replace the top source image with another similar one by double click on it -> File Open -> Select Files -> I browse for a suitable image candidate -> then I click OK
If necessary I make some adjustments here and there and then repeat the procedure above. After some time, depending on the complexity of the transformations and/or number of repetitions I sometimes get a warning from OS that my memory is running low and that I should save my work, etc.
Last time it happened I ignored the warning, as I always do, but this time my PC was serious about it and colapsed. No harm done I just restarted the PC, loaded the last saved workspace script and went on with my work.
However this brings me to a question whether the memory used for building a tree is freed when the source image is replaced. I guess or rather my PC seems to be telling me that probably it is not.
If not, is there any reason why this could not be done? As soon as the image replacement is completed, there is no way to restore the previous tree with transformations and tool touches anyway, so dumping memory no longer needed would be beneficial.
Unless my guesses are wrong and everything is otherwise.
If necessary I make some adjustments here and there and then repeat the procedure above. After some time, depending on the complexity of the transformations and/or number of repetitions I sometimes get a warning from OS that my memory is running low and that I should save my work, etc.
Last time it happened I ignored the warning, as I always do, but this time my PC was serious about it and colapsed. No harm done I just restarted the PC, loaded the last saved workspace script and went on with my work.
However this brings me to a question whether the memory used for building a tree is freed when the source image is replaced. I guess or rather my PC seems to be telling me that probably it is not.
If not, is there any reason why this could not be done? As soon as the image replacement is completed, there is no way to restore the previous tree with transformations and tool touches anyway, so dumping memory no longer needed would be beneficial.
Unless my guesses are wrong and everything is otherwise.