Out of Memory Errors
I am running 32 bit, Windows 7 and 32 bit CO6.3.3 on a new, dedicated, Gigabyte GA-X58A-UD3R desktop motherboard, with Intel dual quad core i7 processors and 12GB of matched memory (6 stix, 2GB each). All of the memory is "seen" by the system. I am post processing 200-300mb RAW images, shot with the IQ180/Mamiya 645DF system. The original RAW files are located on a single, external, 2TB, USB2, Western Digital hard drive. I have gone through the standard, necessary, adjustment slider modifications and, upon hitting the "Process" icon, to send the processed 26" x 35" uncropped images into an external, Western Digital, 2TB HDD, I am getting a lot of frozen CO results. The processing progress bar will start and then stop dead. There are no error dialogue boxes on screen. Once I close out of CO 6.3.3, there are usually about 6-8 identical white Error Boxes on screen, behind the CO desktop screen, with the "Out Of Memory, please close down" message. In the 2TB HDD, I have set up a series of individual folders to receive the processed, 300dpi, 26x35, TIFF images. I let them fill up with about 3.8-4 GB of data before I send the next processed image into an empty folder. There is nothing else running or working on the computer at the time when CO6.3.3 working. I have done only the basic color corrections, exposure density mods and little to no cropping or rotations. Very simple, straight stuff. Occasionally, after I close out of CO6.3.3 and reboot CO6.3.3, once I get back to the CO edit screen and the CO process step, I have noticed that the "process progress bar" has stopped and has remained locked in the same spot where it originally froze up, before I shut it all down. I can't see a way to cancel that previous "process" command without shutting CO down again. What am I doing wrong? I am going to attach a second, 2TB, External, USB2 Western Digital hard drive to the system. I will draw from one "source" drive and process into the second "destination" drive, just in case Win 7 does not want to work with that large file size, into and out of the same 2TB drive. I'll let you know if that resolves the issues. Any other possible solutions? Thanks for the help, Paul
0
-
Paul,
If you are running 32bit OS and Applications your machine will not be able to use all of your memory. The limit will be 2Gb/ 3Gb in total (but not for any single application) if you have set the Use 3Gb variable at the operating system level.
I have no idea how big a TIFF file output will be as a work file when in the conversion process. At a guess it will very very large indeed. Given that I am using 32bit and just about get by with OK performance working with 10 to 14Mb files (although not converting to TIFF very often at all) I suspect you will not see any serious improvement until you change to 64Bit OS and applications.
I have no idea (yet!) how C1 works when converting to TIFF but another application I use will typically create an intermediate workfile of about 140 to 200Mb (or more) from a 10Mb (approx) original RAW file. It can vary quite a lot. If C1 is similar and you are looking at very large start files I would imagine the work files could be very large indeed.
There could be a number of other things influencing what is going on even when you upgrade but quite honestly I don't think anything else makes much sense unless you go to 64bit OS and applications.
(Oh, and maybe see if you can make use of a USB3 or Firewire 800 external drive? Or eSata. Or just put another fast drive into the machine rather than an external drive that will, even if fast for its type, still be much slower than ideal.)
Have you identified whether the external drives are formatted as NTFS? If they are formatted as FAT32 YOU MAY WELL BE COMING UP AGAINST FILE SIZE CONSTRAINTS.
The problems could be elsewhere but it seems reasonable to start form here based on the information provided.
HTH.
Grant Perkins
...................................................................................................................................................................................................................0 -
Hi Paul,
Like Grant said you, window in 32 bits can see all your 12 GO ram but cannot use more than 3 GO. If you want really use all the ram and shoot with big file raw, you need window 64 bits. Very better system and fast !!! (goodbye 32 bits)
Tof0 -
Gentlemen,
Thank you for the tech info. The external USB2 drives are NTFS formatted but if I am only reaching 2-3GB of RAM I am wasting my time. I just uninstalled CO 6.3.3. I have just inserted my 64-bit Win 7 software and will now proceed to load the 64 bit program. There are days when I really do miss the single sheets of 8x10 and 4x5 film. If it isn't one thing, it's another. Excuse me while I go back to square one....0 -
Just thought I would confirm my OS. I am, indeed, running 64bit, Win 7 and have been doing so when these erors started to pop up. Installed memory is 12GB. ( How do I tell if I can access or use all 12Gb of RAM? I'll Google that question.) I will install a couple of internal SATA Hard drives in the morning (11:30p.m. here in CA, USA). The SATAs run 3GB/s instead of USB2 480mb/s, which will be a substantial upgrade. I'll continue to use the matched pairs of external hard drives for my storage of RAWs and processed files. The CO6 was caught in some kind of inescapable "vortex". I shut it down, re-booted (several times) and noted that the processing progress bar was locked in the processing mode for the same picture file, with the little progress bar showing one "hash" mark worth of image processing done. It did not move and, when I went to close the CO6, it noted that it was still processing, did I want to continue the shutdown? When I confirmed the shutdown request, it closed the program and showed 8 "Error" dialogue boxes on the system desktop screen, all stating that there was an "Out of Memory" issue. I'm going to reload CO6.3.3 from a fresh download and, hopefully, limp through the night with my paired external hard drives. Thanks for the heads up on the internal drives. I had forgotten about that potential. Let's see if this changes the system performance at all.
Paul0 -
[quote="NN109526UL2" wrote:
Just thought I would confirm my OS. I am, indeed, running 64bit, Win 7 and have been doing so when these erors started to pop up.
...
I'm going to reload CO6.3.3 from a fresh download and, hopefully, limp through the night with my paired external hard drives.
Paul, can you check whether you run the 32-bit or the 64-bit version of Capture One 6? You reported earlier it was the 32-bit version. If that is the case, you will despite the 64-bit OS, not be able to utilize all RAM but be limited to the 2 GB application space.
Note that a 32-bit application on 64-bit Windows will run in a Windows-on-Windows 32-bits environment, thinking it is dealing with a 32-bit OS. This is by design, otherwise you would not be able to run any 32-bit application on a Windows 64-bit OS.0 -
Thanks, Paul. I was running 32bit CO6.3.3 on the 64bit Windows 7 Pro. I have confirmed that all 12GB of RAM are available and are set as the maximum amount of RAM available. Note that Win 7 Pro can use 192Gb of RAM max. Sweet! OK. Now to download the 64bit version of CO6.3.3. This is all pilot error, I'm afraid.
Side note. All of this tech stuff fascinates me to no end. It is amazing to just read what is going on inside of my i7 dual quad core. Where is it all going? Just 25 years ago, none of this really existed. Amazing.
Paul0 -
That was the ticket. 64bit CO 6.3.3 downloaded and booted normally. 64bit Windows 7 Pro with maxed out RAM. No Error boxes and it is processing at lightning speed. Can't wait to see how fast it runs with internal SATA drives. Thank you all for the help.
Paul0
Post is closed for comments.
Comments
7 comments