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. ⚠️

Memory Leak in 6.3.3

Comments

6 comments

  • Coach
    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
  • Phillip Nondorf
    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.

    P
    0
  • Paul Steunebrink
    Have you tried to do a restart of your system before you start the processing of a batch of few thousand images?
    0
  • NNN634250351094175880
    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
  • Drew Altdo
    I'd suggest you create a support case so we can have a closer look.
    0
  • Phillip Nondorf
    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.