V6 Crash and Absorbs Memory
First of all, I think the upgrade is very good and I like it. However, after loading V6 on my MacPro it seemed unresponsive. Then when working with the Dust/Spot removal, the program crashed on me. Opened the program again and I received a hard failure again. So I decided to watch the program from the Mac Activity monitor and this is what I saw.
First of all, I have a MacPro with 2x2.93 Ghz Quad Core Intel Xeon with 16gig of 1066 DDR3's, Mac OSX is 10.6.5. I am opening a folder with 3,235 raw images of mixed origin for a total of 73.12 gig for this folder. After starting the computer with nothing else running my memory readings were as follows: 14.07 gig Free, 669.6 mb Wired, 847.3 mb Active and 453.6 mb Inactive.
After opening this folder and Capture One VS did all of its stuff and I "just" paged through the images, the system memory was as follows, 1.04 gb Free, 684.5 mb Wired, 4.70 gb Active, 9.52 gb inactive. The only other program open now is Safari and Activity Monitor besides some other small utilities. The folder I am opening resides on a Mac RAID drive via the MAC RAID Card and the drive is 1/2 full. I then opened another folder of approximately the same number of files and seize and while the free memory never went to zero, it came darn close. Closing Capture One I then get a failure message that it closed unexpectedly as there was not enough memory for it to shut down correctly. It did free up about 4 gb of memory.
Next I shut the machine down and restarted the system to get the memory back to where it was. Opened Lightroom with the same file and memory usage hardly budged. Now I have opened Photoshop CS5 with tif file and still have 12.78 gb of free memory......How come CO uses so much memory?
So then I opened CO and it really brought the house down. You know, the kind where the dark curtain comes down the monitor and a black box that tells you your system has failed and you have to hold down the power button to restart it.
First of all, I have a MacPro with 2x2.93 Ghz Quad Core Intel Xeon with 16gig of 1066 DDR3's, Mac OSX is 10.6.5. I am opening a folder with 3,235 raw images of mixed origin for a total of 73.12 gig for this folder. After starting the computer with nothing else running my memory readings were as follows: 14.07 gig Free, 669.6 mb Wired, 847.3 mb Active and 453.6 mb Inactive.
After opening this folder and Capture One VS did all of its stuff and I "just" paged through the images, the system memory was as follows, 1.04 gb Free, 684.5 mb Wired, 4.70 gb Active, 9.52 gb inactive. The only other program open now is Safari and Activity Monitor besides some other small utilities. The folder I am opening resides on a Mac RAID drive via the MAC RAID Card and the drive is 1/2 full. I then opened another folder of approximately the same number of files and seize and while the free memory never went to zero, it came darn close. Closing Capture One I then get a failure message that it closed unexpectedly as there was not enough memory for it to shut down correctly. It did free up about 4 gb of memory.
Next I shut the machine down and restarted the system to get the memory back to where it was. Opened Lightroom with the same file and memory usage hardly budged. Now I have opened Photoshop CS5 with tif file and still have 12.78 gb of free memory......How come CO uses so much memory?
So then I opened CO and it really brought the house down. You know, the kind where the dark curtain comes down the monitor and a black box that tells you your system has failed and you have to hold down the power button to restart it.
0
-
Hi Earl,
In the CO 6 preferences try setting openCL to "NEVER" it seems to fix most problems.0 -
posting.php?mode=reply&f=40&t=9669#
Ok, opened CO6, set the GL preferences to Never, closed CO did a Restart on the MacPro, with no other programs opened, opened CO6 to a folder with 6,743 images of approximately 100 gig, with Canon 5D II and Phase One P45+ raw files. CO6 has not finished building with its load and is has consumed "all" of my system memory and is now using 12 mb of a swap file. I think it is finished loading now, but there is no memory left to do any work.
Sorry, this program is unusable.....I have approximately 200,000 images for approximately 2.4 terabytes. What is the seize of main memory do I have to have to make this thing work, and/or how many files in a folder?0 -
We understand that this should not happen and are investigating.
May be this happens only if you do not have proxies for the images yet and they need to created?
Does a proxy generation activity start automatically (or after a little while) when you select that folder? (menu: WIndow > Activities).
We do recommend that you split your folder to end up with smaller file counts such as 2000 per folder for example.
Hopefully this can help for the time being.0 -
Maybe there is not really a problem? :
Here is more information on inactive memory. It does not mean that it is currently being used now (and can be used by the system at any time) but it means that it was used in the past and is kept around for performance.
http://support.apple.com/kb/HT1342?viewlocale=en_US
Inactive memory
This information in memory is not actively being used, but was recently used.
For example, if you've been using Mail and then quit it, the RAM that Mail was using is marked as Inactive memory. This Inactive memory is available for use by another application, just like Free memory. However, if you open Mail before its Inactive memory is used by a different application, Mail will open quicker because its Inactive memory is converted to Active memory, instead of loading Mail from the slower hard disk0 -
As a reference after loading 2000 images and generating 2000 proxies C1 6.0 will use 2,3GB of RAM. 0 -
Thanks for the responses. The problem is that after the load, I cannot close V6 without it crashing.....
After much work and the help of a program called Trashme, I removed V6 and installed V5.2.1. After the install I selected the same folder mentioned the first time. I also removed the cache, so it had to build this again. Left it along and came back to it, same thing, all the memory is consumed and I now have a 17.2 swap file. MacPro runs slow.
?????0 -
It is obviously an issue of the number of files and their seize within a folder loaded. Just reinstalled V6 without any images and it made a very small dent on the memory use. This will dictate how I use CO; sorted elsewhere and Phase One images loaded into a work file for CO. 0
Post is closed for comments.
Comments
7 comments