Memory Leak in 6.3.3
Heya,
Having a problem with inactive memory and Capture One 6.3.5 running on a new 3.4 Ghz Intel Core i7 iMac. 16 GB of RAM.
I'm trying to process a shoot out to JPGs (non quickproofs), about 6,000 files. Everything works great for about an hour, at which point the inactive memory, which slowly creeps up, finally chews all the available memory and the processing grinds to a screeching halt.
Closing Capture One and restarting the computer seems to be the only way to get things moving along again.
I have tried downgrading to Capture One 6.3.3, but the program acts the same.
Is anyone else experiencing a memory leak in either of these versions of capture one? Are there any remedies that can stop this from happening?
I read elsewhere in the forum about an incompatible video card, and Open CL settings, neither of which seem to be the problem with this machine.
Oh yeah, and I'm running Lion, 10.7.3 FWIW
Thanks!
Phillip
Having a problem with inactive memory and Capture One 6.3.5 running on a new 3.4 Ghz Intel Core i7 iMac. 16 GB of RAM.
I'm trying to process a shoot out to JPGs (non quickproofs), about 6,000 files. Everything works great for about an hour, at which point the inactive memory, which slowly creeps up, finally chews all the available memory and the processing grinds to a screeching halt.
Closing Capture One and restarting the computer seems to be the only way to get things moving along again.
I have tried downgrading to Capture One 6.3.3, but the program acts the same.
Is anyone else experiencing a memory leak in either of these versions of capture one? Are there any remedies that can stop this from happening?
I read elsewhere in the forum about an incompatible video card, and Open CL settings, neither of which seem to be the problem with this machine.
Oh yeah, and I'm running Lion, 10.7.3 FWIW
Thanks!
Phillip
0
-
I use the Windows XP version, but 6.3.2 seems the most stable for my system. Regardless, 6,000 photos at once has got to be pushing things. I don't like working on more than a few hundred at a time. Try making smaller subgroups. 0 -
Thanks, I'll give 6.3.2 a try tomorrow.
Unfortunately because of the workflow, it's not always possible to only do a few hundred at a time. Normally the photographer is shooting all day and the low res files need to be processed over night. If he or she gets shutter happy, batching out a few thousand files is the only way to get it done by morning.
P0 -
Have you tried to do a restart of your system before you start the processing of a batch of few thousand images? 0 -
I've been dealing with the memory leak issue for quite some time. It is absolutely maddening, when I am shooting catalog fashion. I can leave a session open, and watch 10 gigs of RAM trickle down to almost nothing. A shareware app called Ifreemem has helped somewhat, in that it reallocates a couple of gigs. I hope this gets sorted. 0 -
I'd suggest you create a support case so we can have a closer look. 0 -
Sorry for the delayed response, work picked up. Yesterday I installed Capture One 6.4 and processed 1.6k files. The problem seems to have gone away processing wise. The program still steadily chews through the free memory until there are only a few megabytes left, but it no longer stalls between files like it was doing with 6.3.5 or 6.3.3, so processing time was normal.
Is this still typical behavior for a program, to use up all the available free ram like that?
Thanks!0
Post is closed for comments.
Comments
6 comments