Capture One Out of Memory Please Restart
Over the past two days I've been processing a large number of images and have had Capture One tell me it was out of memory and hang three times. I've sent a crash report each time and just filed a case with phase one along with screen captures of my activity monitor.
This happened while modifying images from two seperate Nikon D3's along with a partners Canon 5D's. And never while making changes using the same modification.
I'm running a mid year Mac Pro 3.0 Intel based with 18GB's of ram.
Anyone else having this happen..
Will post when I hear back from phase one.
Lance
This happened while modifying images from two seperate Nikon D3's along with a partners Canon 5D's. And never while making changes using the same modification.
I'm running a mid year Mac Pro 3.0 Intel based with 18GB's of ram.
Anyone else having this happen..
Will post when I hear back from phase one.
Lance
0
-
I have not been until that point because I restart CO4 or my Mac earlier and more often due to more limited resources on my 3 GB RAM MacBook Pro. CO4 Pro and CS3 are happy to eat up all RAM after walking through 100+ images, adjusting, processing and opening/closing in CS3.
I assume however I suffer from the same issue.0 -
[quote="Lance1" wrote:
Over the past two days I've been processing a large number of images and have had Capture One tell me it was out of memory and hang three times. I've sent a crash report each time and just filed a case with phase one along with screen captures of my activity monitor.
This happened while modifying images from two seperate Nikon D3's along with a partners Canon 5D's. And never while making changes using the same modification.
I'm running a mid year Mac Pro 3.0 Intel based with 18GB's of ram.
Anyone else having this happen..
Will post when I hear back from phase one.
Lance
Same here with MacPro Quad core OS X.5.7 CO 4.8.1 and 8 Gb ram…
No Photoshop or any other apps opened.
It appears much less if you divide your worflow with folders having less than 400 files each…0 -
Same problem here, but I'm running 4.8.1 on a Macbook Pro 2.4 Ghz with 4 Gb RAM.
Of course it always seems to happen just as we're about to take "the one".
So you think I need to quit every 100 images? Do I need to restart computer as well as app?0 -
[quote="Lucas12" wrote:
Same problem here, but I'm running 4.8.1 on a Macbook Pro 2.4 Ghz with 4 Gb RAM.
Of course it always seems to happen just as we're about to take "the one".
So you think I need to quit every 100 images? Do I need to restart computer as well as app?
I have now divided my shoots session with no more than 300 files per folder… seems to work nicely since I did that…
Within the "brower" tab, you can create new folders and drag your selected files there, they will bring your settings to the new folder, all together. Handy !0 -
Hey me too, me too!!!! I get that error as well, and Im running an intel mac pro 2x 2.66 dual core intel with 20 gigs of RAM. I laugh when I get that message, not only becasue I know that now i have to wait for C1 to either lock up and force quit it or it falls flat on its face, but also becasue I think the only memory that it could possibly be out of is the fact that its is failing to remember there is 20 frkn gigs worth for it to use if it really felt so inclined to. ahhhh, is it really that tough for a company to just build something that works flawlessly. Id do it myself, but I have no clue how to make a program lol! Someday there will ahve to be the frankensteing of raw converters, take the good parts from each one and slap them together and let it fly 0 -
[quote="garibaldi" wrote:
Hey me too, me too!!!! I get that error as well, and Im running an intel mac pro 2x 2.66 dual core intel with 20 gigs of RAM. I laugh when I get that message, not only becasue I know that now i have to wait for C1 to either lock up and force quit it or it falls flat on its face, but also becasue I think the only memory that it could possibly be out of is the fact that its is failing to remember there is 20 frkn gigs worth for it to use if it really felt so inclined to. ahhhh, is it really that tough for a company to just build something that works flawlessly. Id do it myself, but I have no clue how to make a program lol! Someday there will ahve to be the frankensteing of raw converters, take the good parts from each one and slap them together and let it fly
As post somewhere else, in this forum :
when you get the infamous "capture One gets out of memory, "please restart the application" (or some wording alike), DON'T click "ok" BUT do force quit then you won't make the computer crash and need a hard reset…
Just relaunch C One and you're set quickly back to work…0 -
Yes it is safe to say you should not be running out of memory with 20 gigs! It sounds to me like there may be a memory leak somewhere in your system.. would be interesting to see individual crash reports. We have seen a few cases where the 10.5.7 update did not install correctly and lead to memory leaks. Try downloading the 10.5.7 combo updater again from apple. Create a support case if you are still having trouble and we can escalate to R&D as need be. 0 -
[quote="Jon" wrote:
would be interesting to see individual crash reports.
Not difficult,
how do you want to get it ?
Kind regards0 -
cancelled twin post… 0 -
Hey guys,
Had the same problem but seem to have find the cause on my system anyway.
I also use a MacPro 8 core with 22Gb RAM.
I had a lot of crashes on 10.5.7 and 10.5.8 with C1 from 4.8 up to 4.8.2
I did send in crash reports and the support team was looking into my RAID card that is in my MacPro as the possible cause because this is not supported.
But now I have found that the use of Proof Profile from my Epson 7900 printers made the C1 software very unstable (crash after 4-5 images corrected).
Now I tried to use Adobe RGB as Proof Profile and C1 runs like a dream.
I already posted this info also to Phase One support.
Hope this helps you out there.
Kind greetings,
Bert Balcaen
www.ballena.be0
Post ist für Kommentare geschlossen.
Kommentare
10 Kommentare