Out of Memory
My system has 2gb of memory. With nothing else running, when I open version 4, it reads a directory that is holding about 2.6gb of images in it. It displays on the left the "picture size" is 2.6 gb and after a few moments give me the "out of memory" message and closes down.
Opening up photos in folders with less than 2 gb of images in them seems to work. What is going on. Are we supposed to keep our folders small for Cap 1 (4) to work????
Opening up photos in folders with less than 2 gb of images in them seems to work. What is going on. Are we supposed to keep our folders small for Cap 1 (4) to work????
0
-
Do you have virtual memory turned on in your system? If so, you can add whatever size your page file is to the "memory" available (assuming C1 allows Windows to page-out the unused memory to disk). So if your page file is (eg) 1.5GB, then boy, that means C1's running out of 3.5GB of memory!. In XP and especially Vista, from what I have read, it is actually not disadvantageous to turn on virtual memory (Windows page/swap file) like it used to be in eg Windows 98, because the virtual memory management these days is pretty smart and nifty and generally makes the right choices as to what memory can be paged.
I guess these days with multi-gigabyte memory cards, it's pretty easy to rack up a folder with 2.6GB of raw files (even assuming you use 1 folder per memory card or 1 folder per shoot); heck, some people put all their RAWs in one folder (which admittedly would be a pain when P1 first generates the previews!).
As I see it, C1 would only need to use up to 3 RAW images at a time at the most - one for preview generation, the current image, plus whatever's processing in the batch queue. So either it seems there is some very aggressive and dumb caching going on (ie: irrespective of available memory in a multitasking environment), or do we have some massive memory leak happening here? There have been minor memory leak problems in some early C1 versions, but to be honest I forgot to check this aspect in the betas.
Alternatively, it sounds like it must be keeping all of the previews uncompressed in memory, which probably sounded like a good idea for speed's sake, but maybe the practical implications hadn't been thought through...0 -
[quote="photogenix" wrote:
Do you have virtual memory turned on in your system? If so, you can add whatever size your page file is to the "memory" available (assuming C1 allows Windows to page-out the unused memory to disk). So if your page file is (eg) 1.5GB, then boy, that means C1's running out of 3.5GB of memory!. In XP and especially Vista, from what I have read, it is actually not disadvantageous to turn on virtual memory (Windows page/swap file) like it used to be in eg Windows 98, because the virtual memory management these days is pretty smart and nifty and generally makes the right choices as to what memory can be paged.
I guess these days with multi-gigabyte memory cards, it's pretty easy to rack up a folder with 2.6GB of raw files (even assuming you use 1 folder per memory card or 1 folder per shoot); heck, some people put all their RAWs in one folder (which admittedly would be a pain when P1 first generates the previews!).
As I see it, C1 would only need to use up to 3 RAW images at a time at the most - one for preview generation, the current image, plus whatever's processing in the batch queue. So either it seems there is some very aggressive and dumb caching going on (ie: irrespective of available memory in a multitasking environment), or do we have some massive memory leak happening here? There have been minor memory leak problems in some early C1 versions, but to be honest I forgot to check this aspect in the betas.
Alternatively, it sounds like it must be keeping all of the previews uncompressed in memory, which probably sounded like a good idea for speed's sake, but maybe the practical implications hadn't been thought through...
Thanks,
I guess I'll have to keep the folders smaller until Phase One can figure out how to write software without a mountain of bugs. I especially love the 20-30 pause in Windows before opening.0
Post ist für Kommentare geschlossen.
Kommentare
2 Kommentare