Capture One 22 v15.3.1
I have experienced computer lockup with the latest versions of 22 (15.3.0 and 15.3.1). I am running MacOS Monterey latest version on a 2015 iMac with 32mb of RAM. After experiencing lockups and having to do hard reboot to recover I did some checking using the performance monitor. Whereas v15.2 uses cpu and memory very efficiently, it seems that 15.3 has some major cpu issues. With only the activity monitor and CO running the cpu usage goes way over (indicating 115% which implies a likely memory leak or something similar). I would caution use of 15.3 on older machines and certainly make backups of all your catalog files in case you have to drop back to 15.2 which is what I've done. I'm not sure what the exact cause of the problems are with 15.3 but it is more than likely a bug in the software that is causing excess cpu usage and the lockup of the computer.
Update: I just checked the release notes for CO22 and they do say that Mac is supported for OSX up to 12.2 and that beyond that there could be stability issues. This is most likely to be the problem I have been experiencing as my system is at 12.4. Generally CO is much better about supporting the latest version since they develop on Mac. Hopefully full support for the last version of OSX will be forthcoming.
-
I have exactly the same issue using now 15.3.1 on an iMac of late 2015 running under Monterey 12.4 with 32GB RAM. Rolling back to 15.2 is not an option for me as I have added and edited a lot of pictures to my catalogue after upgrading to 15.3.0 and 15.2 is not able to open the updated catalogue.
Any ideas?
0 -
I have exactly the same lockup issue with the latest versions of 22 (15.3.0 and 15.3.1).
My Macbook Pro 15" 2017 running Mojave .
Every time when i click on a photo must lockup and need a hard reboot .
Any suggestion???
0 -
Bernd and Eric,
Unfortunately, the only solution I found was to drop back to 15.2. When I first had the problem I thought it was just a simple glitch and that maybe it was the age of my computer. Due to my years in computer tech, I made backup copies of all of the CO catalog files as a safety net. When I discovered that the problem seems to be related to cpu hammering by the software I knew that I would need to drop back to 15.2.
If you have been running Time Machine for backups or have offsite backups, the only thing I can suggest is to restore the old catalog files (e.g. xxxx.cocatalog) from backup and drop back to 15.2. In Bernd's case you would lose the edits you made in 15.3 but I don't think there is any way to recover those until CO can address the software issue.
0 -
In the meantime, I have dropped back to 15.2 as well. On my two systems the issue is the same, it is not restricted to older systems. The first version of macOS Monterey had an issue with the memory management esp. with applications changing the shape of the mouse pointer. I have MacOs 12.4 running.
Additionally, my experience is that the issue happened on my systems only with new pictures imported in C1 15.3 - not with the ones which were in the catalogue during the upgrade. And even with the new pictures the issue seems to be restricted to the pictures of my high MP camera, the pictures taken with a lower MP camera imported in C1 15.3 did not trigger the issue.
Rolling back a C1 catalogue is quite easy - when you accept to loose the development settings of the pictures imported in the new version. The old catalogue is a part of of the new catalogue. Right click on the catalogue in the MacOS Finder and choose the option to show the packet content. You will see all the catalogues as backups which were generated during the C1 upgrades since you are using that catalogue. In my case, I have deleted "xxx.cocatalogdb" and renamed "xxx.cocatalogdb.backup 9" back into "xxx.cocatalogdb" and got my C1 15.2 catalogue back.
0 -
Brend,
Glad you are able to get functioning again. The fact that you indicated the issue with high megapixel images is a good indicator of the problem. The high cpu usage and likely the paging into the disk would be indicative of the memory issue. All of my images are from Canon 5DSR and R5 cameras so at roughly 50MP for all images. I do have some lower pixel count frames from about 10 years ago but didn't try those. Thanks for the tip on dropping back to the older version. That's is easier than copying gigs of data back and forth.
0 -
Hi George,
I have indeed the feeling that the bug is coming from the combination of high MP cameras (my one is the Leica M11 with 60 MP) and the generation of the previews in C1 15.3. Older pictures taken with the M11 before I have upgraded to C1 15.3 which I have imported e. g. in May 2022 with C1 15.2 worked without any problems in C1 15.3. Obviously, the previews were generated in C1 15.2 and just opened in C1 15.3.
0 -
Hi Bernd,
That's an interesting observation but I wonder if it is a factor. The lockup occurs during image processing not on import (at least in my case). However, when CO 15.3 starts it hammers the cpu which indicates that it is more related to a code issue than the image size per se. When I opened 15.3 the first time I had it update the catalog and that went very smoothly. It was only when I started processing images that problems arose. The problem, in my opinion is at code issue that is not handling memory management correctly.
0 -
Hi George,
I haven't checked the memory usage when I started C1 15.3. As you say, the issue occurs during processing of the images, not during the import. But my system is very slow and crashes in the end only when I process images which I have imported in C1 15.3. When I process older images, which I have imported some weeks ago in C1 15.2 - which were in the catalogue (DNGs on a NAS in a file structure) when I upgraded to C1 15.3 - I haven't seen any issues. The processing of these older images is as fast as it is in C1 15.2 and my system did not crash.
0 -
Bernd and Eric,
I think Bernd might have hit on the problem which might be related to how CO is processing the high res images and handling the database.
I looked at my preferences for the image tab and the preview size was at 5120 which is the recommend size for the 5K iMac screen. The default on a Mac retina screen is actually 2560 which is half the resolution and the computer handles the display to make things look smoother. I set the preview size to 2560 and then started 15.3.1 again and everything loaded quickly and no problems. After working with the new program for several minutes I loaded my 2021 catalog and things went very well with the upgrade. The 2020 catalog loaded ok but the computer froze after a couple of minutes. After the reboot I started CO again and everything worked fine with the 2020 catalog. I loaded the 2019 catalog and after it was loaded I quit CO and restarted it. No issues with the program.
My assumption is that the software still has a problem with memory management or something, but by changing the resolution of the preview images to the native display of the computer (you can look up the way 4K/5K actually works to understand this) CO works fine. At least so far I have not had any further problems.
Let me know if this works for you guys.
George
0 -
Hi George,
that clearly fits in the picture I have recognized. My assumption is as well that C1 15.3 has an issue with the memory management. Keeping the previews smaller helps during processing of an image because C1 would need much less memory per processing step if the previews are just a quarter of the standard setting.
Bernd
0 -
I upgraded to 15.3.1 yesterday. Today I experienced sluggishness when trying to import 10 files from a Leica SL typ 601 and twenty files from a Leica M10M. It should have taken less than 60 seconds and it was a few minutes.
This MacBook Pro is running 11.6.4 Big Sur OS, Last of the intel chips 2019, 32GB Ram, Graphics Card Radeon Pro 550M.
Occurred while referencing files into a session and when I opened my current catalog to update with new images.0 -
This is all useful information, and listening to all the issues convinced me to wait on updating. But in addition to posting here, and alerting fellow users to beware of 15.3x, I hope you guys are all submitting bug reports so that the C1 guys actually start fixing things.
I do suspect that much of this may stem from adding Metal support for Intel Macs. I don't see the same number of complaints from people using Apple Silicon Macs, which have had Metal support from the beginning.
0 -
I have the same problems on my MacMini late 2014 (macOS Monterey 12.4). Turning off hardware acceleration seems to solve the problem for me. In the release notes for CO 22 15.3 it is said that they switched hardware acceleration from OpenCL to Metal even on Intel based Macs ("Metal support on Intel (Mac)"). So this seems to be the root of all the trouble. I open a support ticket for that.
0 -
Hey Guys,
My problem solved by turn off hardware acceleration.
After i set hardware acceleration (Display and Processing) set to never . Everything goes smooth .
Then i try to set hardware acceleration (Processing) Auto again ,my Macbook Pro still work properly.It seems the lockup issue is coming from hardware acceleration (Display) setting. Turn that setting to never may help.
0 -
Eric and Olaf,
I think you have confirmed the issue that I raised about the monitor display The two may be related due to the way Metal works vs OpenCL. The hardware ecceleration would be related to the display aspects as Eric found out. Thanks for opening the ticket Olaf.
0 -
As a follow up to this issue. I have found that I needed to disable hardware acceleration for screen display in order to keep from getting a lockup. Thanks to Eric for finding this solution.
0
Please sign in to leave a comment.
Comments
16 comments