Capture One 9 PRO a memory hog?
Downloaded and installed CO9 PRO and getting out of memory messages much more frequently with only a couple of other apps running. I have 16 gigs, Windows 7 64 pro, i7-2600 box so it should have enough muscle...Anyone else?
0
-
[quote="John490" wrote:
Downloaded and installed CO9 PRO and getting out of memory messages much more frequently with only a couple of other apps running. I have 16 gigs, Windows 7 64 pro, i7-2600 box so it should have enough muscle...Anyone else?
I see that it uses most of my 8GB memory, but don't have gotten out of memory msg's. I don't find this a problem if C1 is keeping a good eye on the used memory (some cache I suppose).0 -
Thanks for sharing this.
I can't speak for C1 v9 but v8 uses much more memory than any other application I ever ran, especially when processing images and particularly with several layer masks. I do have once in a while OOM messages from Windows 7 stating that I should close applications, and then often crashes from either C1 or another application if I am not quick enough.
Windows 7, 8 GB RAM. Have upgraded with SSD a while ago (with a nice performance boost) but RAM cannot be extended.
Meanwhile I always run task manager and have an eye on the used memory in order to close C1 when it approaches 8 GB, just to avoid OOM. It also slows down then, probably due to swapping RAM to disk.
Sometimes, after every out processing there is some memory leak, not reused by susbsequent out processesing, task manager shows a stairway/ step up every time. I process the same image quite often to see the end result after having made changes.
It seems to be image dependent, as sometimes I can see a re-decline in memory consumption after processing (as it should be). So the issue is not really reproducible.
I am willing to upgrade to C1 v9 BUT NOT if that means I have to buy a new machine with higher specs, which costs more than 10 times the license upgrade!
cheers,
BeO0 -
I upped the swap file, shutdown orderly and rebooted. With Thunderbird in the background (multiple email addresses) and in and out of Chrome, I was able go through a post session (dual recipes) without incident. I will keep an eye on it for a while and update this post if anything changes. 0 -
I have yet to check 9 but V8, running on Win 7 with 2 or 3, sometimes more SESSIONS open (albiet it not the huge RAW files that many here will be deploying) has hardly ever been a problem - certainly not recently.
Typically there will be several other general applications running and Firefox with many tabs open.
I do have 24Gb of RAM. I can easily get to 16Gb in use but hardly ever approach 24Gb. This on a Dell Precision notebook with i7 but not useful Graphics card on which to deploy OpenCL. (It has one but there's not enough power in it to make it worth deploying.)
I suspect that 16Gb or more RAM is highly advisable to get the best out of the hardware when loading things up. This particular machine has 4 slots, so 2 spare on delivery, and the memory slots are intended to be accessible to users albiet not without some dismantling. It came with 8. Ran OK but the temptation to go for an extra 16 for some other workk I was using it for was too strong to resist.
I'll load up V9 in a few days and see what happens.
Grant0 -
I'm trying out capture 9 on a number of Xeon Win 7 PCs with 32Gb of RAM. So far it seems only a matter of time before Capture 9 eats all the available memory and causes the system to pop up a memory message and lose data. If I close Capture and re-open it does release the memory and I can carry on. Best before it runs out as other programmes tend to close prematurely when windows runs out of memory. 0 -
We have found a leak when using Canon raw files. We are looking into it, and can hopefully include a fix in a not too distant service release. 0 -
[quote="Christian Gruner" wrote:
We have found a leak when using Canon raw files. We are looking into it, and can hopefully include a fix in a not too distant service release.
I see the usage climb with Nikon files, but with lot's of local adjustments. Because I have only time for rather short PP sessions, I now only do a couple of images per "run".
If I have time I'll try longer this evening.0 -
[quote="Christian Gruner" wrote:
We have found a leak when using Canon raw files. We are looking into it, and can hopefully include a fix in a not too distant service release.
Thanks Christian for informing us. Very much appreciated!
Is this a new memory leak present only in C1 9 or does this exist in C1 8 too?
I have my memory eating issues (described above) with C1 8 and with Sony raw files, and if I remember correctly with Nikon NEF files too.
Thanks and regards,
BeO0 -
[quote="BeO" wrote:
[quote="Christian Gruner" wrote:
We have found a leak when using Canon raw files. We are looking into it, and can hopefully include a fix in a not too distant service release.
Thanks Christian for informing us. Very much appreciated!
Is this a new memory leak present only in C1 9 or does this exist in C1 8 too?
I have my memory eating issues (described above) with C1 8 and with Sony raw files, and if I remember correctly with Nikon NEF files too.
Thanks and regards,
BeO
Only in 9.0.00 -
[quote="Alain" wrote:
[quote="Christian Gruner" wrote:
We have found a leak when using Canon raw files. We are looking into it, and can hopefully include a fix in a not too distant service release.
I see the usage climb with Nikon files, but with lot's of local adjustments. Because I have only time for rather short PP sessions, I now only do a couple of images per "run".
If I have time I'll try longer this evening.
We have not seen the issue with Nikon files.0 -
I have had very similar issues uusing CO8 with Olympus ORF files - and 32GB DDR3 memory. Thought I had a virus, then suspected a lowly HD 7850 card, and a slow disk. Changed both the latter, and its better, but I still see task mgr showing c. 28 Gb memory use!
So not really keen to use CO9 if the same continues.
Mark0 -
[quote="Christian Gruner" wrote:
[quote="Alain" wrote:
[quote="Christian Gruner" wrote:
We have found a leak when using Canon raw files. We are looking into it, and can hopefully include a fix in a not too distant service release.
I see the usage climb with Nikon files, but with lot's of local adjustments. Because I have only time for rather short PP sessions, I now only do a couple of images per "run".
If I have time I'll try longer this evening.
We have not seen the issue with Nikon files.
Indeed no memory leak, but a constant high usage of -on my computer- available memory. Seems ok to me, better to use it than to have it unused.0 -
[quote="Christian Gruner" wrote:
We have found a leak when using Canon raw files. We are looking into it, and can hopefully include a fix in a not too distant service release.
Thanks...I was using Canon RAW, so I will be wayching for the update.0 -
I have the same problem. I am working with Canon RAW-files, and in this session I was using Local Adjustments with 3 layers. Windows joblist reported 13,5 gb memory usage.
Then i closed Capture One, and started it again and Windows joblist reported 1,5 gb memory usage.
When i continued working with Local Adjustment Layers them memory increases rapidly.
I'm also looking forward to an update 😊
Torben0 -
I'm trying out the Capture One Pro trial. Imported my lightroom catalog which has 1000s of canon raw files. I'm unable to generate previews, after a few minutes I get an out of memory issue. 16gig RAM somewhat highend desktop system. No other apps open. I imagine this is the same issue everyone else is having.
Hope you guys fix it soon. I'm interested in purchasing but currently this bug is preventing me from probably trialing the software 😉
cheers0 -
8 7D2 Images in a folder, 3 adjustment layers on each. C1 using 7.7GB and climbing
ImgCoreProcess at 1.2GB and climbing
HOW did this get released with such a huge bug?0 -
I am processing Canon 5DSR raw files and version 9 does have a memory leak and the processing of a large amount of files is problematic. This was not the case with version 8. Hope a fix comes out soon. 0 -
I won't be hitting the upgrade button until this is fixed! 0 -
I'm Nikon D7100 User (24 MPix) files and C1 9.0 has same problem with memory:
5 Images need more than 3GByte Memory and rising.
Crashes very often.
With LX100 (12 MPix) I need more files to reach +3Gbyte,
but still much higher requierments than 8.0
With C1 8.0 I process 500+ Files in a single run with less than 3 Gbyte.
Currently I regret the upgrade from 8.0 to 9.0!0 -
[quote="NN635443198636745898UL" wrote:
I'm Nikon D7100 User (24 MPix) files and C1 9.0 has same problem with memory:
5 Images need more than 3GByte Memory and rising.
Crashes very often.
With LX100 (12 MPix) I need more files to reach +3Gbyte,
but still much higher requierments than 8.0
With C1 8.0 I process 500+ Files in a single run with less than 3 Gbyte.
Currently I regret the upgrade from 8.0 to 9.0!
Please create a support-case for crashing, that should of course not happen.
The 3 gb of ram is normal, and I would not consider it excessive. An application using ram is not in itself a bad thing, please have that in mind. Quality of an application cannot be judged by the amount of ram consumed.0 -
Please create a support-case for crashing, that should of course not happen.
The 3 gb of ram is normal, and I would not consider it excessive. An application using ram is not in itself a bad thing, please have that in mind. Quality of an application cannot be judged by the amount of ram consumed.
Thank you for getting a direct reply from the test team!
My current problem with C1 9.0 is the difference of RAM usage from C1 8.3 to C1 9.0 with Nikon D7100 files when starting to use cropping, white balance adjustment, Highlight and shadow adjustment and then processing.
And in my opinion the amount of RAM consumed by an application is one parameter for judging the quality of an application. It defines the additional cost for Hardware and the total speed of image processing. Since there are a lot of other parameters, and C1 shines on a lot of them, the bottom lines is still positive.
I also understand the difficult work of the test team and the importance of a reproduceable crash scenario. But it will take some time to generate a useful support case.
One additional question: Do you have scripted (automated) test scenarios for C1?0 -
[quote="NN635443198636745898UL" wrote:
Please create a support-case for crashing, that should of course not happen.
The 3 gb of ram is normal, and I would not consider it excessive. An application using ram is not in itself a bad thing, please have that in mind. Quality of an application cannot be judged by the amount of ram consumed.
Thank you for getting a direct reply from the test team!
My current problem with C1 9.0 is the difference of RAM usage from C1 8.3 to C1 9.0 with Nikon D7100 files when starting to use cropping, white balance adjustment, Highlight and shadow adjustment and then processing.
And in my opinion the amount of RAM consumed by an application is one parameter for judging the quality of an application. It defines the additional cost for Hardware and the total speed of image processing. Since there are a lot of other parameters, and C1 shines on a lot of them, the bottom lines is still positive.
I also understand the difficult work of the test team and the importance of a reproduceable crash scenario. But it will take some time to generate a useful support case.
One additional question: Do you have scripted (automated) test scenarios for C1?
Keeping relevant things in ram, ready to use, makes an application faster, not slower. If the RAM was clearly at every given step, the application of course not use much ram, but the data needed would have to be either read from disk, with much much slower I/O speed, or re-computed, using additional and unnecessary CPU-resources.
Of course leaking is completely different story, but in case of your 3 gb extra usage, that is very likely not the case.
We use a lot of automated testing, both during testing and during development. We also use a lot of manual testing, as far from all test-activities can be or should be automated.0 -
With Version 9 I often hear the GPU/CPU fan increasing in noise (like when doing GPU rendering) and the CPU is at 100% leaving no ability to control any other applications. On Windows 7 the green horizontal bar behind the icon (that indicates rendering of image recipes) grows from left to right when I haven't directed the software to render anything.
Not sure what to do to resolve this issue so any ideas are very welcome.0 -
May be because accidentally you pressed shortcut to start export. 0 -
Another one with CO1 memory leaking issues, and not a Canon user, but Pentax and Sony.
I have 16gb of RAM installed, and after working in CO1 for about an hour, I got the Windows warning that I was short of memory, and telling me to save open files and specifically shut down CO1 to not lose any work. First ever with this machine.
So some work to do for the engineers at Phase one.
Chris0 -
Also found that as you continue working any adjustment takes longer and longer ☹️ 0 -
Chriswo, which RAW files, Canon or others? 0 -
[quote="BeO" wrote:
Chriswo, which RAW files, Canon or others?
Nikon0 -
So, thought I'd put Capture One V9 through it's paces with 717 images from a 7D MK2 (CR2)
https://www.youtube.com/watch?v=5Chd9q6Hbn4
26GB of memory usage? (have to close Capture One to get that back as ImgCoreProcess.exe likes to hang on to it for some reason?)
And then I put Capture One V8.3.4 though it's paces with 1151 images from the same 7D MK2 (CR2) - different folder because I'd upgraded the other to V9
https://www.youtube.com/watch?v=0HHGh9jCftU
not even 1GB of memory usage!!
Don't feel you need to sit through them, unless you like watching numbers tick by 😉
Process Recipe is JPEG 100% - Embed Camera Profile - Res 300ppi at 100% - processed to the same destination drive (the C1 V8 files are on an external eSATA drive)0 -
Hi there
So the consensus on this thread is that v9 has a big problem? So why hasn't Phase withdrawn it? Where is there a clear statement that Phase accepts there is a problem?
With all this uncertainty I for one will not be trying v9. No way am I volunteering to be an unpaid b-tester!
Peter0
Post is closed for comments.
Comments
46 comments