Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Out of Memory errors 6.3.2

NN101583UL3
Just updated from 6.0 to 6.3 and I am now getting an out of memory error and C1 freezes, requiring a restart of C1.
When it is resarted it has lost all my settings and adjustments that I have done to the one image in the capture folder!
I then get another out of memory error asking me to restart C1, I say OK and C1 continues as normal.

What on earth is going on with the latest version!!!
0

Comments

9 comments

Date Votes
  • Drew Altdo
    What is your OS?
    How much RAM do you have?

    Depending on the actions you are asking Capture One to do, the size and quantity of the file and the amount of RAM available in your system you could very well be simply running out of RAM.
    0
  • NN101583UL3
    I am using XP pro and 4 Gb RAM.

    But I think you have missed my point. I was using 6.0 with no memory errors whatsoever.
    And suddenly now that I am using 6.3 I get memory errors and C1 crashes.
    I can only presume 6.3 has been written to use excessively large amounts of memory, therefore causing these crashes.
    Is there any way that the user can control how much memory this version uses?
    0
  • Drew Altdo
    If you reference the release notes, the amount of RAM necessary for Capture One 6 is 2GB where the amount of RAM necessary for Capture One 6.3 is 4GB. The software has indeed changed through these versions to offer more features and thus requires more RAM.
    Again, depending on what you are doing to the images and the size of the images and available RAM at the time (due to other applications running) you may be running out of RAM. Since you are on the XP platform there are restrictions to what memory can be accessed and many people (including myself) have found that adjusting your system to allow the use of more RAM drastically improves performance. The link below is helpful in that regard;
    http://dwf.blogs.com/beyond_the_paper/2 ... vista.html
    0
  • SFA
    Hmm.

    Just installed V6.3.2 on a 5 year old HP notebook running Win7 32 bit with 2Gb memory and a slighty older Dell Optiplex GX620 running Win 7 32 bit with 3Gb memory and so far the notebook has not crashed or shown any errors I can recall but the Dell is very fragile and really dislikes Local Adjustments. The desktop is not running any other user applications - it was set up to be a dedicated photo processing station.

    I do appreciate that the recommendation is for 4Gb RAM and a 64bit system bit since the notebookk seems to be surviving wiht less memory and a similar level of 2 core processor I would really like to understand what it is about the desktop machine that is causing it to fail frequently before settling on a specification for an upgrade. It is set to use all 3 Gb of ram and the Usage monitor shows that both cores are working hard and that at the point the crashes occur the system has circa 800Mb of memory 'free'.

    I suspect that the Error message is not pointing accurately to the problem so if anyone has any ideas about what to check I would be very grateful. It will help me to spec. the replacement.
    Grant
    0
  • Jim MSP
    [quote="SFA" wrote:
    Hmm.

    ........
    I would really like to understand what it is about the desktop machine that is causing it to fail frequently before settling on a specification for an upgrade. ...... It will help me to spec. the replacement.
    Grant

    Unfortunately, I can't really help you with understanding the memory problem. All I can do is help you spec a new desktop by telling you what I have that I am happy with; and 6.3.2 works quite well on it. I have a crash every so often (1 per month), non reproducible, and seems to be related to bringing in a new image quickly after another one, and the "focusing" hangs up. This only seems to happen when CO is using >1.5G of memory as seen by the Windows resource manager.
    I have:
    A Dell Studio XPS 425T/9000 desktop
    WIn 7 Pro 64 bit
    Intel I7 cpu 920
    8G Memory
    a 1TB Seagate HD, partitioned to C & F, with C only having software (no photos)
    a ATI Radeon HD 5700 graphics card

    I can run CO, Media Pro, and PS Elements all at the same time with no problem.

    I sometimes run 6.3 on a small Dell XP laptop with 4G, and it runs ok, but v slowly.

    Good luck,

    Jim
    0
  • JonS
    a 1TB Seagate HD, partitioned to C & F, with C only having software (no photos)


    For both stability and performance reasons, it is best to have two separate physical hard drives for the OS and photos, and not two partitions on the same hard drive.
    0
  • SFA
    [quote="Jim MSP" wrote:
    Unfortunately, I can't really help you with understanding the memory problem. All I can do is help you spec a new desktop by telling you what I have that I am happy with; and 6.3.2 works quite well on it. I have a crash every so often (1 per month), non reproducible, and seems to be related to bringing in a new image quickly after another one, and the "focusing" hangs up. This only seems to happen when CO is using >1.5G of memory as seen by the Windows resource manager.



    Thanks Jim. The spec will be useful and I think I need to study the cost/performance implications of the graphics card options as well. Currently I'm running ATI Radeon HD 4300/4500 Series so scope for improvement.

    I also have a Touchscreen monitor and reading some other posts I wonder if this may be an influencer too.

    With C1 V5 I had similar issues (which did not change with the addition of the touchscreen monitor) along the lines that you outlined above. It seemed to be more prevalent when working on folder with a large numbers of files but of course, being a relatively random occurrence and without understanding the factors that influence the process, it was always a 'surprise' when things froze and then crashed. Once in a while things would recover. I think spotting the possible problem with only one too many keystrokes would allow recovering, three or 4 typed before the condition was recognised guaranteed a crash. Of course I can't be sure of that.

    I fully expect this to be a configuration issue ... bit it may also be like looking for the proverbial needle in a haystack in a field full of haystacks. My guess would be memory management since the CPU usage meter I have running sems to suggest that free memory is not an issue (it's crashing showing 800+ Mb available out of 3Gb) and from time to time I have seen things running with only about 100Mb 'free' in the system when other user apps (as opposed to just the normal system processes) are also running.

    As a problem it's not unique to C1 but does seem to be a slightly more common experience than I was hoping for. My crash rate is somewhat higher than yours but there are so many differences that comparison is probably not reasonable.

    Interestingly the 1.5Gb memory thing is, from memory and subject to be incorrect recall, something that Java (I think) based programs suffer from as original Java could not address more then 1.5GB of RAM.

    I'm still puzzled as to why the notebook seems to be OK with just 2Gb RAM. Maybe I should set the desktop limit to 2Gb and see what happens.

    I'll run some more experiments later - other things to do today.

    Thanks for you help!


    Grant
    0
  • SFA
    [quote="JonS" wrote:
    a 1TB Seagate HD, partitioned to C & F, with C only having software (no photos)


    For both stability and performance reasons, it is best to have two separate physical hard drives for the OS and photos, and not two partitions on the same hard drive.



    Agreed.

    I have 2x1TB internal drives and although, when space constrained, I do use the capacity of the 'Program drive' I try to keep things separate, shifting 'Legacy shoots' to external drives to free up space when required.

    Thanks for the input Jon.
    0
  • Jim MSP
    [quote="JonS" wrote:
    a 1TB Seagate HD, partitioned to C & F, with C only having software (no photos)


    For both stability and performance reasons, it is best to have two separate physical hard drives for the OS and photos, and not two partitions on the same hard drive.


    I agree. And when the budget allows, it will be the next add.
    However, it works well for me at this time, and that was the main message.
    0

Post is closed for comments.