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

CO freezes and unable to force quit on Mac

Permanently deleted user
Hi, how are you doing.
I have a problem and hope that someone will be able and kind enough to help.

As I called for applying Color tags to 400 images, CO 10 pro just freezes.

Cannot quit, cannot force quit, cannot even restart my Mac... it says I have to quit CO first, wich I tried for the past hour to no avail.
Tried to kill the process in Activity monitor, but CO does not appear anywhere but in my dock as an active application.

If anyone can help it will be much appreciate!

Thank you all and good evening
0

Comments

3 comments

Date Votes
  • OptionalAlias
    Sorry to hear that you have problems.

    I had the same when doing a larger change in a catalog trying to split it as CO was unbearable slow.
    Total hang and nothing to do but force quit which worked for me. Although it also killed the catalog with all referenced photos and CO was unable to repair it.

    I had to start over.

    You can always kill the process in terminal with:

    sudo kill -9 <pid>

    Replace <pid> With the process ID of the frozen CO process.

    If that does not work there are even more aggressive ways but some are destructive.
    0
  • Eric Nepean
    [quote="NNN635112270368285093" wrote:
    Hi, how are you doing.
    I have a problem and hope that someone will be able and kind enough to help.

    As I called for applying Color tags to 400 images, CO 10 pro just freezes.

    Cannot quit, cannot force quit, cannot even restart my Mac... it says I have to quit CO first, wich I tried for the past hour to no avail.
    Tried to kill the process in Activity monitor, but CO does not appear anywhere but in my dock as an active application.

    If anyone can help it will be much appreciate!

    Thank you all and good evening


    Hopefully if the proces does not show in activity monitor, the catalog may not be damaged. Otherwise you may have to recover from backup. (I do a backup veryday that Ise COP)

    The first challenge is to find the process ID of of Capture one, then you use that to kill it, as follows:

    First you start Terminal, you will find it in /Applications/Utilities.

    In terminal, type the following: pgrep -l "Capture"
    This will print out a short list of all running processes having a name containing "Capture", see my output below. In the list, you should find "Capture One 10" - note the process ID (pid), which will be the first number in the line - in this example it is 24019, yours will be different.

    7577 Image Capture E
    13451 Image Capture E
    24019 Capture One 10
    24025 CaptureCoreServ

    Then type sudo kill -9 <pid> in my case: sudo kill -9 24019

    Terminal will ask you to enter your admin password, and then it should kill Capture One.
    0
  • Permanently deleted user
    We have had similar issues with freezes. If you have upgraded from a previous version of C1 make sure you remove the old
    preferences. Option click on the Go tab and select Library, open Preferences and delete:

    com.phaseone.captureone9.LSSharedFileList.plist
    com.phaseone.captureone9.plist

    Restart and relaunch C1 10.

    There seems to be some conflict with old preferences.
    This is something I have noticed with previous version upgrades.

    Try this too:
    In C1 preferences, under General, change "open CL" settings from auto to never.

    Hope this helps.
    0

Post is closed for comments.