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

macOS 13.2.1 (22D68) Memory Leak during Cull

BVR

I was culling around 1500 images from a GFX 100S (mix of RAF and JPG) files, and after about 20 minutes of this Capture One had used about 32gb of memory and the force quit applications window came up (with Capture One being non-responsive). So far I've been able to replicate it even after rebooting.

1

Comments

4 comments

Date Votes
  • Andrew Mitchell

    I just had the same issue while shooting tethered with a Canon R5. At one point CO was using 39GB!  Very frustrating as I had to constantly watch Activity monitor and quit CO as I saw memory usage get out of hand. Otherwise it would freeze up CO or even crash the computer. I contacted support and they said it's known bug and they are working on it. He said he can't guarantee it will be in the next service update which I kind of took to mean it won't be. He pointed me to their message board where it's listed.  https://support.captureone.com/hc/en-us/community/topics/9492608977949-Noticeboard  They did get back to me rather quickly which at least that was nice.

    Andrew

    0
  • Andrew Mitchell

    I've found a fix for this memory leak issue for those that are experiencing it. My memory usage was jumping by anywhere from 250MB to 1 GB with every tethered capture. I tried updating CO from 16.1.1 to 16.2.1 but was the exact same problem. I then did a complete uninstall of CO by following their instructions:  

    https://support.captureone.com/hc/en-us/articles/360002402377-How-do-I-uninstall-Capture-One-      

    Then reinstalled 16.2.1 and all seems good! Although I am worried that it will come back but for now able to work again with CO. I recommend others with this problem to try the same. 

    Andrew

    0
  • BVR

    I did this as well as restarted before re-installing C1, it looks like the leak is significantly slower yet still there. I went from ~2gb of usage and after culling around a thousand photos it had consumed around 16.6gb (and rising) I'll just have to work with activity monitor open and keep restarting C1 it looks like. 🫠

    0
  • BVR

    It also appears to climb faster with Groups turned off? This is hardly scientific but 🤷‍♂️

    0

Post is closed for comments.