Constant crashing since moving to 20
I upgraded a few days ago and everything seemed okay, but since last evening C1 20 is now crashing constantly, in fact from this morning I can't even fire it up without it crashing immediately. No error messages, just a crash. I tried reinstalling, but still doing the same.
Anyone else seen this, or have any ideas?
Anyone else seen this, or have any ideas?
0
-
An update - the problem is with the catalog. When I take one of my old Capture 12 catalogs and upgrade it to v20 then C1 works again and stops crashing. Is there a catalog repair tool or something? 0 -
Yes there is a catalog repair tool. File>Verify catalog or session. The catalog or session you are trying to repair can't be open at the time.
Ian0 -
Thanks Ian!
Just in case it helps others I've tracked down exactly what's causing the issue to occur. If you have an image open, go into the Styles menu, and then go down through the styles by hovering your mouse over each one to get a feel for the style, that will cause a crash - sometimes immediately, sometimes after going through a quite a few previews. In some cases this also somehow corrupts the catalog, in others just restarting the app is fine.0 -
Tidal wrote:
Thanks Ian!
Just in case it helps others I've tracked down exactly what's causing the issue to occur. If you have an image open, go into the Styles menu, and then go down through the styles by hovering your mouse over each one to get a feel for the style, that will cause a crash - sometimes immediately, sometimes after going through a quite a few previews. In some cases this also somehow corrupts the catalog, in others just restarting the app is fine.
My crashing issue occurs when I try to make an adjustment to an image while zoomed in, but maybe it's somehow related. I'll try the catalog update.0 -
As a side note, I hope you all send in all the crash reports, assuming the crash report tool popped up after the crash. Crash reports are all processed by R&D and are crucial in improving the stability of the program. 0 -
Could you get an idea from Logs generated by macOS, you can find them under user/library/logs/diagnosticreports
I am experiencing the same issue, contact crash.
What OS are you using, any change of Catalina?0 -
fatihayoglu wrote:
Could you get an idea from Logs generated by macOS, you can find them under user/library/logs/diagnosticreports
I am experiencing the same issue, contact crash.
What OS are you using, any change of Catalina?
Only that it's the opencl_runtime crashing the GPU. Given the problem is in opencl I have disabled Hardware Acceleration (Preferences... > General)
This appears to prevent the crashes and is, for now, a workaround. I think you can probably just disable it for 'Processing' and leave it enabled for 'Display', but C1 has caused me enough headaches today that I'm leaving them both disabled for now.
And, yeah i'm using Catalina.0 -
Support responded with the following recommendation: Try deleting the ImageCore cache folder at /Users/Shared/Capture One/ImageCore. This should force the application to rebuild the ImageCore cache on the next launch.
This resolved the issue for me
(including here in case anyone else does a search on this problem in the future)0 -
Tidal wrote:
Support responded with the following recommendation:Try deleting the ImageCore cache folder at /Users/Shared/Capture One/ImageCore. This should force the application to rebuild the ImageCore cache on the next launch.
This resolved the issue for me
Thanks for sharing this, Tidal.
The interesting part is that this is the location for the CO 12 image core (and earlier versions). CO 20 stores its image core in the user's profile under /Users/<user_name>/Library/Application Support/Capture One/ImageCore/13.0.0
Note that now under the ../ImageCore folder there is a subfolder for the release.
Apparently, the old (CO 12) image core still affects CO 20. That is weird.0 -
yeah it was definitely referencing the old CO 12 location in the logs I sent.
Anyway, after a day of trouble-free operation....it's started crashing again. I'm just going to leave the HW Acceleration disabled. That seems to work. Really they need to fix this.0 -
try to update 10.15.2, that has solved my problem (which TS confirmed it is a OpenCL problem) 0 -
There was a new release today. 13.1.1 but my C1 crashes when renaming files. The file renames but the sequence does not change. When resetting the sequence counter and renaming C1 crashes.
Richard C
0
Post is closed for comments.
Comments
12 comments