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

Capture Crashes On Opening

Larry Hayden
Hi,

I've got a problem that I can't seem to address. Capture One crashes on start up.

I'm on a Mac with 10.7.5 and version 7.1.6 running on CO. Any advice would be greatly appreciated.

It appears that my data bus is corrupted in some fashion. I can open CO just fine with a new session or a new catalog.

Larry
0

Comments

12 comments

Date Votes
  • Paul Steunebrink
    First line of defense: repair permissions from Disk Utility.
    -1
  • Larry Hayden
    Hi Paul,

    Yes, I did that. I've also verified the database and it checked out OK. What appears to be happening, according to what I can make out of the crash log, is that there is an endless loop happening. The last action I took, before closing CO, was to add metadata information to a selection of images. All was working fine when I closed CO.

    I'm using the backup catalog to restore but it's taking awhile to rebuild the previews. I only have 3000 images in this DB and luckily have every image backed up so I didn't lose anything but my image import for about 700 images, their ratings and adjustments and whatever else was done to them.

    I'm hoping to be able to repair the existing DB but it looks like it's toast.

    Thanks,

    Larry
    0
  • Miles2
    I have a similar issue. I am trying to build a catalog that references images from multiple sessions and have had now to build four such catalogs because each one suddenly starts 'killing' Capture One on startup when I briefly see a screen which is different from what I was last using. So I have had to start building a new catalog to replicate the previous one. Just work from the best part of four days gone to waste so far.

    The files are referenced so the original images are still on disk (and backed up0 but it's stopping me pulling together images from five years of sessions that I want to edit and re-process for a new website.

    Is there a way to verify the catalog from outside of C1 ?

    I've submitted a number of crash reports to Phase One but there's been no acknowledgement as yet.
    0
  • SFA
    [quote="Miles2" wrote:


    I've submitted a number of crash reports to Phase One but there's been no acknowledgement as yet.


    Miles,

    By crash reports do you mean the automated sort of reports that pop up and ask if you want to send information to the software supply company?

    If so that may not help you. They are just reports not personal support cases.

    Have you created a support case with the Capture One support team?


    Grant
    0
  • Miles2
    Grant,

    Yes it was initially the automated reports but last night I opened a support case and got a prompt reply from Phase One this morning. Sadly, it doesn't really shed any light on what might be the problem. I've provided some more observations so will see.

    Miles
    0
  • PaulB
    I've had the same problem with corrupt catalogs not allowing CO7.2 to open. It has happened three times now. Not sure why. Once I had made LOTS of changes to settings and ratings and color labels to several hundred images in one sitting, and I closed CO at the end of the day, and I'm thinking CO did not have enough time to process through all of those changes, so it then got "confused" and unable to open.

    The most recent time, I had deleted several hundred images from the catalog and closed CO, and again, I think I did not give it enough time to process those changes. However in both cases, there was no progress bar or rotating circle to let me know it was still processing anything. But my hunch is that it was.

    In the first case I WAS actually able to open the corrupt catalog by doing this: Every time I tried to open CO, the CO screen would appear briefly and then disappear and CO would shutdown. So one time, I tried clicking on the CO screen when it appeared and held down the mouse button, just to see what would happen. Eventually, all of the images appeared and it seemed to be running fine. It worked!

    But the last time it has crashed, I never even got the CO screen to appear at all, so I tried to open the backup catalog. Well THAT was nightmare because the default backup folder is buried/invisible in the Mac OS!!! I had to ask out studio tech expert where it was and he told me to use the terminal window utility and a specialized command to get it to show up in my finder. THAT seems poorly designed!!! 🤬 ).

    So MY QUESTION: That backup catalog seems to have a more complicated structure with other settings and proxies folders, so I don't want to move it from it's hard to find Backup Folder location. How do I move that back-up catalog to a more user friendly location in the finder????
    0
  • Paul Steunebrink
    [quote="PaulB" wrote:
    ...
    I had to ask out studio tech expert where it was and he told me to use the terminal window utility and a specialized command to get it to show up in my finder. THAT seems poorly designed!

    By default, the backup of the catalog file is stored in the user's Library folder. A few version of OS X ago, Snow Leopard I believe, Apple decided to make that folder hidden by default. You can easily unhide it (temporarily) from Finder. A terminal command unhides it permanently. Google for 'hidden library os x' and you're set.
    [quote="PaulB" wrote:

    So MY QUESTION: That backup catalog seems to have a more complicated structure with other settings and proxies folders, so I don't want to move it from it's hard to find Backup Folder location. How do I move that back-up catalog to a more user friendly location in the finder?

    You can define the backup location form Capture One's preferences, General tab.
    0
  • Permanently deleted user
    I too am having this same problem, here's a link to my recent post:
    viewtopic.php?f=46&t=16041&p=75737&sid=1e20dd788a07d8eacd582278b8c44e97#p75737

    I've had a support case opened for 4 days, and we're going through a number of troubleshooting tasks including uploading my "corrupt" catalog to the techs. Turns out the catalog isn't damaged, and it looks like Capture One is developing a glitch somehow and failing/crashing on catalogs at some point. This is the second time I've had this crashing upon opening issue happen, the first a few months back.

    Overwriting with backup catalogs won't solve the problem, as the problem exists within the software (best guess at this point) and not the catalog DB.

    I'm still currently working through this with tech support and will let you know what is discovered.
    0
  • PaulB
    Thanks for the update. Let them know I'd be happy to send them my corrupt catalogs as well.
    0
  • Jason Watts
    I had a similar problem recently. All of a sudden C1 crashed on start up trying to open my main catalog. I tried verifying the catalog and everything looked OK. Same thing happened after a couple of times using various back ups of the catalog.

    I opened a support case and eventually sent the catalog to Phase One. They could not replicate the problem and found the catalog to be free of corruption. The problem was suggested to be the linking with the root folder of photos on my data drive. Changing the name of that root folder and re pairing the photos to the catalog has fixed he problem. Might work for you too.

    Open a support case if all else fails. It took over a week to sort out (mainly because I was otherwise busy with my day job!) but they got me back on track.

    Jason
    0
  • Permanently deleted user
    Jason-

    When you changed the root folder name, you are saying you changed the name of the folder your photos were in? Did CO then not crash and allowed you to locate the photos? Every time I try something, CO crashes when attempting to open the problem catalog (even though the catalog checks out green/verified).
    0
  • Jason Watts
    Yes. When I changed the root name of the folder my RAW files are stored in I got it all working again. The first couple of attempts, it crashed again before I had a chance to relocate the files. So I changed it back to its original name feeling frustrated and the catalog opened again (go figure?). I then decided to change to another name as I figured the Phase One guys were right in suggesting it was some error between the catalog and the storage location. The catalog then allowed me to locate the files. It's been working ever since (touch wood!).
    0

Post is closed for comments.