Out of Memory error with PWP5
Posted: July 8th, 2009, 6:25 pm
I haven't seen any references to this type of error on the board; so I'll ask:
I have been seeing "Out of Memory" errors with PWP5 (5.0.1.4) under certain circumstances. I have a 32-bit WinXP PC with 2GB RAM. I open a raw file from my Canon 5D2, perform a series of transformations, then save the file. I close all the windows using the Window -> Close All selection, and move on to the next raw file.
If the transformations I perform are all progressive (that is, if I don't go back and perform two or more transformations on the same image somewhere along the transformation history), then I have never seen an "Out of Memory" error.
If, however, I do perform two transformations on the same image (because I don't like the outcome of the first transformation), then even after I Window -> Close All, more likely than not I get an "Out of Memory" error when I try to open the next raw file. The only recovery seems to be to restart PWP5.
I don't remember seeing anything like this with PWP3.5 where I worked on large TIFFs produced by Canon's DPP (I've never used PWP4). Is this memory fragmentation?
Thanks,
Max
I have been seeing "Out of Memory" errors with PWP5 (5.0.1.4) under certain circumstances. I have a 32-bit WinXP PC with 2GB RAM. I open a raw file from my Canon 5D2, perform a series of transformations, then save the file. I close all the windows using the Window -> Close All selection, and move on to the next raw file.
If the transformations I perform are all progressive (that is, if I don't go back and perform two or more transformations on the same image somewhere along the transformation history), then I have never seen an "Out of Memory" error.
If, however, I do perform two transformations on the same image (because I don't like the outcome of the first transformation), then even after I Window -> Close All, more likely than not I get an "Out of Memory" error when I try to open the next raw file. The only recovery seems to be to restart PWP5.
I don't remember seeing anything like this with PWP3.5 where I worked on large TIFFs produced by Canon's DPP (I've never used PWP4). Is this memory fragmentation?
Thanks,
Max