Capture ONE Express (Sony) Crashes when closing on Apple M1 MacBook Air

Comments

7 comments

  • Dennis van Mierlo

    I have the same issue with the C1 Pro edition on my Mac Mini M1. C1 freezes when closing and I have to force quit C1. I do not know if the C1 database connection is already closed at that time. Otherwise, it might get corrupted. I filed a service request for this.

    0
    Comment actions Permalink
  • SFA

    Do you have any Catalog backup settings applied?

    Have you looked at the log files to see what activities are in progress at the time of closure and crash?

    0
    Comment actions Permalink
  • Dennis van Mierlo

    I do have a backup strategy for my photos and C1 catalog database. But this does not prevent the database from getting corrupted when C1 crashes when closing.

    0
    Comment actions Permalink
  • SFA

    Dennis,

    Has the internal Capture One backup finished when the system freezes and you kill the process?

    Other than that, have you run the Catalog verification process to see if Capture One has anything to report that might be relevant to the freeze problem?

    Other than those factors and the potential for some challenges for whatever is currently required to make software reliable with the new Mac technology the only way one might work out where things are not working as expected would be to analyze the log files.

    0
    Comment actions Permalink
  • Dennis van Mierlo

    Hi SFA,

    The catalog verification result is OK. So, it does not seem to have an impact on the integrity. That makes me happy :-)

    In the Capture One forum thread Will Capture One run on my ARM-based Apple computer? user Maarten Heijkoop made the suggestion to set both display and processing hardware acceleration to Never. I have done this and this seems to help. Capture One closes normally now. I am going to see how other Capture One functions are running.

    Lot’s of greetings, Dennis 🇳🇱 

    0
    Comment actions Permalink
  • Dennis van Mierlo

    Hi SFA,

    When closing down Capture One, it seems that backing up the catalog takes a long time, about 5 minutes to complete. Looking in the logs (Console app) I see the entries below.

    I notice that the error "2021-02-28 13:41:11> (ERROR) Failed to load film-curve []" occurs during the catalog backup procedure. I do not know if this has an impact on the duration of the backup.

    Log Reports - com.captureone.captureone14.log
    =============================================
    2021-02-28 13:38:44.154 *** Initiating Capture One Termination Procedure ***
    2021-02-28 13:38:44.162 Activity threads finished shutdown
    2021-02-28 13:38:44.162 Shutdown BatchQueue started
    2021-02-28 13:38:44.162 Shutdown BatchQueue finished
    2021-02-28 13:38:44.289 Waiting for threads to exit
    2021-02-28 13:38:44.289 Threads done
    2021-02-28 13:38:44.305 Autosaving /Users/<path_to_catalog>.cocatalogdb
    2021-02-28 13:38:46.463 Autosaving /Users/<path_to_catalog>.cocatalogdb
    2021-02-28 13:38:46.476 Waiting for background saving to complete...
    2021-02-28 13:38:46.496 Background saving done.
    2021-02-28 13:43:23.024 Autosaving /Users/<path_to_catalog>.cocatalogdb
    2021-02-28 13:43:23.048 Waiting for background saving to complete...
    2021-02-28 13:43:23.071 Background saving done.
    2021-02-28 13:43:31.830 Autosaving /Users/<path_to_catalog>.cocatalogdb
    2021-02-28 13:43:31.866 Initiating CamerasManager shutdown procedure
    2021-02-28 13:43:31.866 Terminating capture service with token 1703421667
    2021-02-28 13:43:31.869
    2021-02-28 13:43:31.869 *** ENDED ***
    2021-02-28 13:43:31.869


    Log Reports - CaptureOneIC.log
    ==============================
    2021-02-28 13:41:11> (ERROR) Failed to load film-curve []
    2021-02-28 13:41:11> (WARNING) No color profile in input; assuming sRGB.
    2021-02-28 13:43:31> Ending worker: TileExecuter 0 [POProxyManager processor] (master: (30b65c000), worker: (312821000))
    2021-02-28 13:43:31> Shutting down: TileExecuter 0 [POProxyManager processor] (master: (30b65c000), worker: (312821000))
    2021-02-28 13:43:32> Ending worker: TileExecuter 0 [PYRAMID_Automask processor] (master: (30b65c000), worker: (3102fa000))
    2021-02-28 13:43:32> Ending worker: TileExecuter 0 [PYRAMID_PackageSamplerProcessor1] (master: (30e2e2000), worker: (3106fd000))
    2021-02-28 13:43:32> Ending worker: TileExecuter 0 [PackageSamplerProcessor1] (master: (30e2e2000), worker: (310b00000))
    2021-02-28 13:43:32> Ending worker: TileExecuter 0 [POSharedPickerGenerator] (master: UI, worker: (311306000))
    2021-02-28 13:43:32> Ending worker: TileExecuter 0 [PackageBitmapCPUProcessor0] (master: (30c1ab000), worker: (30c9b1000))
    2021-02-28 13:43:32> Ending worker: TileExecuter 0 [PackageSamplerProcessor0] (master: (30c1ab000), worker: (30d2d6000))
    2021-02-28 13:43:32> Ending worker: TileExecuter 0 [PYRAMID_PackageSamplerProcessor0] (master: (30c1ab000), worker: (30dedf000))
    2021-02-28 13:43:32> Ending worker: TileExecuter 0 [PYRAMID_PackageBitmapCPUProcessor1] (master: (30e2e2000), worker: (30eae8000))
    2021-02-28 13:43:32> Ending worker: TileExecuter 0 [Automask processor] (master: (30b020000), worker: (30d6d9000))
    2021-02-28 13:43:32> Ending worker: TileExecuter 0 [PYRAMID_PackageBitmapCPUProcessor0] (master: (30c1ab000), worker: (30dadc000))
    2021-02-28 13:43:32> Ending worker: TileExecuter 0 [PackageBitmapCPUProcessor1] (master: (30e2e2000), worker: (30eeeb000))
    2021-02-28 13:43:32> Shutting down: TileExecuter 0 [PackageBitmapCPUProcessor0] (master: (30c1ab000), worker: (30c9b1000))
    2021-02-28 13:43:32> Shutting down: TileExecuter 0 [PackageBitmapCPUProcessor0] (master: (30c1ab000), worker: (30f2ee000))
    2021-02-28 13:43:32> Ending worker: TileExecuter 0 [PackageBitmapCPUProcessor0] (master: (30c1ab000), worker: (30f2ee000))
    2021-02-28 13:43:32> Shutting down: TileExecuter 0 [PackageSamplerProcessor0] (master: (30c1ab000), worker: (30d2d6000))
    2021-02-28 13:43:32> Shutting down: TileExecuter 0 [PackageSamplerProcessor0] (master: (30c1ab000), worker: (30f6f1000))
    2021-02-28 13:43:32> Ending worker: TileExecuter 0 [PackageSamplerProcessor0] (master: (30c1ab000), worker: (30f6f1000))
    2021-02-28 13:43:32> Shutting down: TileExecuter 0 [PYRAMID_PackageBitmapCPUProcessor0] (master: (30c1ab000), worker: (30dadc000))
    2021-02-28 13:43:32> Shutting down: TileExecuter 0 [PYRAMID_PackageBitmapCPUProcessor0] (master: (30c1ab000), worker: (30fef7000))
    2021-02-28 13:43:32> Ending worker: TileExecuter 0 [PYRAMID_PackageBitmapCPUProcessor0] (master: (30c1ab000), worker: (30fef7000))
    2021-02-28 13:43:32> Shutting down: TileExecuter 0 [PYRAMID_PackageSamplerProcessor0] (master: (30c1ab000), worker: (30dedf000))
    2021-02-28 13:43:32> Shutting down: TileExecuter 0 [PYRAMID_PackageSamplerProcessor0] (master: (30c1ab000), worker: (311b0c000))
    2021-02-28 13:43:32> Ending worker: TileExecuter 0 [PYRAMID_PackageSamplerProcessor0] (master: (30c1ab000), worker: (311b0c000))
    2021-02-28 13:43:32> Shutting down: TileExecuter 0 [Automask processor] (master: (30b020000), worker: (30d6d9000))
    2021-02-28 13:43:32> Shutting down: TileExecuter 0 [PackageBitmapCPUProcessor1] (master: (30e2e2000), worker: (30eeeb000))
    2021-02-28 13:43:32> Shutting down: TileExecuter 0 [PackageBitmapCPUProcessor1] (master: (30e2e2000), worker: (30faf4000))
    2021-02-28 13:43:32> Ending worker: TileExecuter 0 [PackageBitmapCPUProcessor1] (master: (30e2e2000), worker: (30faf4000))
    2021-02-28 13:43:32> Shutting down: TileExecuter 0 [PackageSamplerProcessor1] (master: (30e2e2000), worker: (310b00000))
    2021-02-28 13:43:32> Shutting down: TileExecuter 0 [PackageSamplerProcessor1] (master: (30e2e2000), worker: (310f03000))
    2021-02-28 13:43:32> Ending worker: TileExecuter 0 [PackageSamplerProcessor1] (master: (30e2e2000), worker: (310f03000))
    2021-02-28 13:43:32> Shutting down: TileExecuter 0 [PYRAMID_PackageBitmapCPUProcessor1] (master: (30e2e2000), worker: (30eae8000))
    2021-02-28 13:43:32> Shutting down: TileExecuter 0 [PYRAMID_PackageBitmapCPUProcessor1] (master: (30e2e2000), worker: (311f0f000))
    2021-02-28 13:43:32> Ending worker: TileExecuter 0 [PYRAMID_PackageBitmapCPUProcessor1] (master: (30e2e2000), worker: (311f0f000))
    2021-02-28 13:43:32> Shutting down: TileExecuter 0 [PYRAMID_Automask processor] (master: (30b65c000), worker: (3102fa000))
    2021-02-28 13:43:32> Shutting down: TileExecuter 0 [PYRAMID_PackageSamplerProcessor1] (master: (30e2e2000), worker: (3106fd000))
    2021-02-28 13:43:32> Shutting down: TileExecuter 0 [POSharedPickerGenerator] (master: UI, worker: (311306000))
    2021-02-28 13:43:32> Shutting down: TileExecuter 0 [POSharedPickerGenerator] (master: UI, worker: (311709000))
    2021-02-28 13:43:32> Ending worker: TileExecuter 0 [POSharedPickerGenerator] (master: UI, worker: (311709000))

    0
    Comment actions Permalink
  • SFA

    Hi Dennis,

    Please do not assume that I correct in this suggestion but I think your "close" activity would relate to the log file entries timed at 13:43.31 and thereafter so the shutdown log recording either stops at part of the process and therefore further log entries do not occur OR it has completed but background processes are not all shot down; OR, for some reason, the end of the shutdown does not close the master process even though the job is complete.

    Now, from time to time I see something similar with my Windows machine but they tend to be random events and not repeatable at will. So far as I can tell all other C1 related processes will have been closed and disappear from the list of running programs and all log files seem to indicate successful completion. 

    When it happens more than once in consecutive closure operations (extremely rare) my normal routine is to shut down C1 and the system and restart. I assume that there may be some undesirable temp and work files orphaned by the failure to complete the close and so getting Windows/Capture One to tidy up as they restart seems like a good idea.

    If I were you I would still seek clarification through the Support Channel but if the Catalog is not locked the next time you attempt to open it, it may be safe to assume that the last process did indeed finish.

    0
    Comment actions Permalink

Please sign in to leave a comment.