Constant Crashing even after completes Mac OS reinstall
Hi I'm running Capture One v22 on a 2019 Mac Pro, it crashing constantly, I even went as far as doing an entire OS reinstall after doing clean installs of the app but still, it crashes like crazy sometimes every 10 minutes. I keep writing in the bug reports but thinking that's useless as updates have happened but still the issue persists.
I have the catalogues running on a Samsung T5 SSD, this has also been reformatted.
What on earth can I do!
-
Maybe it helps if you recreate the cache:
On MacOS right click the catalog file and choose "Show package contents"
You will find a directory named "Cache" in the package. Delete it (or move it to another location outside the catalog) and create a new directory "Cache" in the package.
You will lose your previews but C1 will recreate them when needed.
1 -
Can you press+hold the key Alt to open C1 without any catalog and see it is crashes? (Alt key is Windows but there is a equivalent Mac key for this)
Can you copy one of the catalogs to your internal disk to see if it also crashes when opening it there?
1 -
Thanks Mario and BeO, I'll try both suggestions and will let you know, one catalogue is too big to go on the internal disk
0 -
Do you have your images imported into the catalog (they appear in the collection "In catalog") or referenced ("Add to catalog" on import)?
0 -
I have the same problem , start from V20. I have multiple catalogs. Recreate catalog seems to me helps for short time. But really for short. Capture One never able to solve my problem. 3 cases. Non of them solved
0 -
@BeO I have all the images in the catalogue.
I tried deleting the cache but it has made no difference. for this project, I've had to resort to editing my photos in Affinity Photo as Capture One just does not cut it anymore,
No one from the technical team has got back to me with a fix, despite numerous requests on the crash feedback forms.0 -
Rupert,
This is mainly a User to User forum.
The OS generic crash feedback forms are not personalised requests for support - they are just generic feedbacks for performance and statistical analysis. Usually treated as anonymized.
You should seek personalised support via a Support Case system. Use the "Submit a Request" feature of the Community pages to create the request and attach the details required to assist the analysis.
0 -
SFA I know this is, I'm talking about the crash reports generated when the app crashes. I put down an email address in my reports. so one every 10 minutes might make them take note that there's a problem but to no avail. So I gave up.
0 -
They are not considered to be "official" reports by the OS vendor let alone the Application vendor.
Providing an email address is a nice courtesy just in case one of the reports does elicit a reply but the chance of that is likely to be miniscule. Or smaller.
My guess would be that you have some conflicting system settings - possibly some dynamics settings in something like the plists (userconfig files in Windows) and they will be carried forward despite re-installations.
It could also be a problem with some other types of user specific personalisations or something related to the source files or their edits.
I'm Windows user. Once, a decade ago, I had a session that was crashing every ten minutes (or rather every 10 images or so). It turned out to be a bad edit instruction file for a single image in a set of over 3000 images, where the data block on disk had become corrupt as it was written. The effect was to call it up for use for every tenth image and at that point it would usually deliver incompatible data that could not be trapped, thus crashing the application and the whole computer.
When I eventually spotted the problem image (because it had a slightly corrupt thumbnail that would not repair) I deleted the files concerned, re-imported the original image and re-edited without any further problems.
Problems with data blocks in the storage are rare but if they occur can be very difficult to completely identify and will often result in seemingly random system crashes for which the source of the problem may not be at all obvious.
At a simpler level, do you use custom Workspaces? Especially any brought forward from older versions of C1?
0 -
How do I find these bad blocks, im guessing using Tech Tool Pro, would be the way forward, in this situation, I have removed Pref files before but it made no difference.
can you please advise me on how im to go about these diagnostic tasks. Thanks.0
投稿コメントは受け付けていません。
コメント
10件のコメント