C1 23 has a memory leak
Whilst shooting tethered memory runs full, never happened before.
MBP M1 Max 16“ 2022 fullspec.
Its not just once, it happens continuously. Need to halt session and restart everything in front of my clients - neeeds fix ASAP please!!
-
Frank Schroeter: Auto sync sidecar XMP is set to None so unfortunately not the source of my memory leak problem.
0 -
Andrew Mitchell (and everyone), are you using any metadata in your workflow, like copying metadata from the previous capture through Next Capture Adjustments?
0 -
Frank Schroeter- Yes, I do that on most jobs including the ones I've had the issue on.
0 -
Hey Frank, thanks for asking! Yes, I do. I have my copyright informations, with address, website etc. on. Also, I always copy the previous camera settings and adjustments when shooting tethered in the studio.
0 -
Hey Frank Schroeter
one of my machines does use metadata, the two others don`t.
And one machine does not use tethering, but the import function directs to the memory leaking.
0 -
Frank Schroeter We don't use extra Metadata information such as IPTC. We just copy through the adjustments while shooting tethered.
0 -
Frank Schroeter I discovered, that the memory used get reduced by deleting previously shoot files. I guess thats again an indication to the preview images.
Has Capture One found any possible reasons for the memory leak?
When can we expect a fix to that problem?
1 -
Sebastian Zell, we are investigating this issue with highest priority. But we have still not found a root cause in our code. Thus I cannot say if or when we will have a fix. As I said earlier in this thread, there is one relevant change to memory management in 16.2.0, which is currently in beta and will be generally available soon. More changes are in the pipeline and will come with 16.2.1. Beyond that, I can only recommend to always install the latest macOS updates. MacOS on Apple Silicon has a lot of memory issues of its own that Apple is weeding out one by one.
0 -
We have now identified a number of issues and fixed them for 16.2.0. Please give that a shot once it becomes available and report back if your problem is fixed or not.
0 -
Thanks Frank Schroeter for the Update. We are looking forward to get the Update :)
0 -
That is indeed great! Thanks for your efforts, Frank Schroeter
0 -
Unfortunately 16.2.0.112 has made this issue even worse.
Mac Studio ultra running 12.6.3
1 -
Ray Hardy, please contact Capture One support and give them the details. I also recommend you update your OS, if not to Ventura, then at least to the latest Monterey build.
For most people 16.2.0 seems to be an improvement. But we are not done, more related changes are in the pipeline.
0 -
Same problem with "Memory Full"
Mac M1 64gig RAM. OS 13.3.1
with C1Pro 16.2
Canon r5
0 -
We have further memory-related changes in the pipeline, but they will not make it into 16.2.1. If you are still affected, please check out 16.2.2 when that comes.
1 -
Frank Schroeter Thank you for the troubleshooting and updates, it is much appreciated and good to know you are working on a fix for this.
In the meantime, is there any recourse for affected customers in relation to a discount or reduction on the monthly rates while we are unable to use the software within its intended potential?
Thus far my only workaround to avoid memory crashes has been rolling back to Capture 22. This has obviously made it incredibly difficult in regards to session compatibility with the many other photo professionals I work with and disrupted workflow in general.0 -
Scott Heldorf, I cannot comment on that. Please reach out to our customer support.
0 -
Frank Schroeter Thanks for the updates. We all hope 16.2.2 will be available soon and fix the problem.
Scott Heldorf I still rely on C1 23. My workaround is a constant monitoring on the activity window on Mac.
As long C1 doesn't reach 100GB on my MacBookPro (M1 Max, 32 GB) all works fine. As it gets close to 90GB I'll close and reopen C1 real quick. Else if I miss it the whole system breaks down...
0 -
Sebastian Zell
Thank you, and I am aware of this workaround.
If I worked on relaxed shoots that would be fine. Unfortunately I work in a very high paced shooting environment and can't just expect the photographer & talent to stop and wait while I restart software every 10-15 mins (this is basically how long it takes to consume enough memory to crash). This means the client monitor also drops out, as well as the general workflow of the shoot.
Not only is it embarassing for me as a digi-op but it's also not a good look in front of paying clients.
At this stage my only real option is to use C22 until the issue is fixed.0 -
Since my last post a month ago I have done a full disk uninstall of every previous version and preference, and a clean install of each subsequent version of C1. I ended up going back to an earlier version - 16.0.2 for stability. This seemed to help a little bit but I was still slowly filling up with memory after just 100 images or so. And that's after setting the Preview resolution lower. Yesterday, right before a job, I updated to the latest version of C1- 16.2.0.2 with the latest version of Monterey- 12.6.6 per recommendations from earlier in this thread. The new version is still leaking and the program was still comparatively slow and glitchy. It was taking 5-8 seconds to resolve images from R5 that historically popped up really fast and hesitation when changing tool tabs or folders. My client yesterday was, fortunately, a meticulous shooter so I was able to monitor the memory usage. When it got high I was able to quietly restart C1 to clear the memory. I did, however, allow it to lock up several times at the end of the day just to make sure it's still happening. And, I am using the XMP full sync.
2021 MacBookPro 16" M1 Max/64GB/4TB/ Monterey 12.6.6 - Commercial Digital Tech
0 -
Frank Schroeter is there any known correlation to Rosetta? I reset my MacBook M1 Pro to 13.4 with no Rosetta installed and did not receive any Memory Leakings so far. but on all other machines with rosetta installed, Im still running into this issue. Maybe such a rosetta-free install would be a workaround, if it works.
0 -
Konstantin Odin I'm sticking to Monterey 12.5.1, but memory is also leaking...
0 -
Just had the same issue during the shoot today. 100gb of memory used, latest version both system and c1, maxed out m1max
0 -
Konstantin Odin, no, we are not aware of a relation to Rosetta. But this may be something people who are still affected can try: Run the app in Rosetta instead of native. Performance will be lower, but if the RAM does not fill up then, maybe it is a net improvement.
You do this by right-clicking the app icon (while the app is not running), select Information and set the checkmark on Open with Rosetta. Then macOS emulates a x86 environment and CO runs the code for Intel Mac.
0 -
Hello,
I've just had the same issue when on set with 2x 27" 4K Monitors+iPad, 2021 MacBookPro 16" M1 Max/64GB/4TB/ Monterey 12.3 using C1 16.2.0112. I was trying to optimise memory by shutting down every other app but C1. (not the latest MacOS nor C1 version, I know but read below)
I've had this message approximately twice a day saying the computer was out of ram memory (over 70GB RAM) when on set dealing with a large amount of folders containing a fair amount of pictures (sometimes up to 600).
It didn't happened when shooting. But only when browsing pictures and selecting pictures. When the message popped up, it was already too late, totally frozzed the computer and needed to force restart the machine, losing the color tags and stars having been done in the last 5-10 minutes prior to the crash :/ Not really professional in front of the Clients, Art Directors, Photographers,...
I'm thinking of going back to CO22 or even CO21 which was way more stable and reliable and had a way much better UI not the Lightroom/childish style which is not so professional anymore :(
I know a lot a Digitechs having had the same issue but decided to not report it yet. The thing is, we professionals, using C1 on a daily basis, don't need to upgrade our systems every month or even twice a year. We are often still using CO21 or CO22 because our machines are populated by softwares used in a professional environment. Deciding to upgrade the OS or only ONE program can have a terrible effect on the whole ecosystem. Stability, reliability and performance is the key.
Hope this issue will be fixed soon otherwise, we — the daily users — will be more reluctant than ever to stick to your monthly subscription or any other update if it has not being tested on a full scale for at least 6 months.
Thanks in advance !
Best,
A Professional Digital Technician
3 -
My only current solution has been to roll back to C1 22. The current C1 23 is unusable on my system in a professional envionment.
I would highly suggest any other photo professionals & digi-ops like myself to contact the C1 Customer service team and request a reduction in your monthly subscription. I have done this now and I am waiting on hearing back from them with an update.
Maybe some financial pressure from customers will expediate the resolution process.1 -
I have the same issue. Macbook pro 16, m1 max, 32 gb. 1 tb. Capture One last version. Capture One 23 is unusable right now. All my friends have the same issue and use C1 22.
0 -
Having a similar issue on a maxed out M2 MacBook Pro. This seems to be a common issue among everyone I know.
1 -
Happens regularly to me just importing images from camera SD card. Today I tried importing 289 images (full resolution thumbnails). Using the new Cull import process and picking photos to import, it maxed out memory after selecting about 90 images. I tried the same card and photos again just clicking on select all and it imported all 289 images and did previews quickly and never had a memory problem. I think I’ll just keep importing the old way (Bypass the new import process) until the memory issue is resolved.
Mac mini M2 Pro, 32GB memory, Ventura 13.4, Cap One 23 (16.2.1.13)
0 -
Hey all - same issue for me been happening for a while now and my assistant (rightly) keeps getting annoyed that I have not complained to C1 about it. I shoot several times per week and it was happening about 3 times per shoot since updating to C1 23... now thanks to a so called fix suggestion/update after raising a ticket with C1 support it happens 5-6 times per shoot. I have gotten used to closing it and reopening it quickly but as everyone else has said this is not good enough. I have my clients following along on their laptops with the online capture pilot and the connection keeps being interrupted when I have to close and open again. Also if I fail to notice that it has popped up with the force quit dialogue box and continue shooting it completely crashes my mac and have to hard restart it. No Bueno.
1
Please sign in to leave a comment.
Comments
71 comments