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

COP8 now unstable since update to OSX10.9.5

jknights
All through the beta testing COP8 was very stable but recently I updated to OSX10.9.5 and now my COP8 has become hugely unstable.

Please can this be confirmed by other users and if so please report to Support by raising a new case.
0

Comments

9 comments

Date Votes
  • jknights
    I have raised a Case report and sent in crash logs.
    0
  • jknights
    This seems to be the offending process.

    Thread 31 Crashed:: -[POProxyManager proxyCreationThread:] Dispatch queue: POProxyGenerator create queue
    0 libsystem_kernel.dylib 0x00007fff8a62a866 __pthread_kill + 10
    1 libsystem_pthread.dylib 0x00007fff8bfcb35c pthread_kill + 92
    2 libsystem_c.dylib 0x00007fff87fb9b1a abort + 125
    3 libsystem_malloc.dylib 0x00007fff88cde07f free + 411
    4 ImageCore.dylib 0x00000001086016c2 0x1084a9000 + 1410754
    5 ImageCore.dylib 0x0000000108fae92a 0x1084a9000 + 11557162
    6 ImageCore.dylib 0x0000000108615c28 0x1084a9000 + 1494056
    7 ImageCore.dylib 0x0000000108615a3e 0x1084a9000 + 1493566
    8 ImageCore.dylib 0x00000001085a1a54 0x1084a9000 + 1018452
    9 ImageCore.dylib 0x00000001085b1375 0x1084a9000 + 1082229
    10 ImageCore.dylib 0x000000010859622a 0x1084a9000 + 971306
    11 ImageCore.dylib 0x000000010885385b 0x1084a9000 + 3844187
    12 ImageCore.dylib 0x0000000108559eb8 ICP_CreateFileProxy + 152
    13 com.phaseone.captureone8 0x00000001070eb344 __60-[POProxyGenerator createProxyForImagePath:proxyPath:force:]_block_invoke + 573
    14 libdispatch.dylib 0x00007fff8eadd28d _dispatch_client_callout + 8
    15 libdispatch.dylib 0x00007fff8eae3a18 _dispatch_barrier_sync_f_slow + 460
    16 com.phaseone.captureone8 0x00000001070eb0e7 -[POProxyGenerator createProxyForImagePath:proxyPath:force:] + 135
    17 com.phaseone.captureone8 0x00000001070e8f4e -[POProxyManager proxyCreationThread:] + 427
    18 com.apple.Foundation 0x00007fff8ab8cdfb __NSThread__main__ + 1318
    19 libsystem_pthread.dylib 0x00007fff8bfca899 _pthread_body + 138
    20 libsystem_pthread.dylib 0x00007fff8bfca72a _pthread_start + 137
    21 libsystem_pthread.dylib 0x00007fff8bfcefc9 thread_start + 13
    0
  • Alan Disler
    I have been running COP8 in trial mode for 5 days on a 2013 MacPro running OSX 10.9.5 and have also experienced several crashes while in different functions and one which caused a complete system freeze requiring a shutdown and reboot.

    -Alan D.
    0
  • Ario
    I have Capture One 8 installed on two different machines both running 10.9.5 and since the installation (the day of CO8 launch) I have experienced only one application crash while I was using the cloning tool. I am using only catalogs and no tethering.
    0
  • NNN635003982619074238
    I have been running various versions of Capture One for 7 years and 10 months without one single crash or application error. Capture 8 is no exception to a fine heritage of Phase 1 programmers. I hope to bequeath my C1-8 license keys to my grandchildren so they can share the experience.
    0
  • Paul Steunebrink
    So far no issues CO Pro 8.0 with 10.9.5
    0
  • jknights
    I think I have discovered the problem.
    I had some Fuji X100S that had been sent to me for testing. These images had been adjusted so they were B&W even when delivered as RAW. COP8 was seeing that they werent correct and was crashing.
    I would have thought that it would exclude them as 'corrupt' images instead of crashing.


    A thought for the developers. If the image data doesnt parse correctly then mark the image in the browser as corrupt or unrecognised!!!
    0
  • SFA
    [quote="jknights" wrote:
    I think I have discovered the problem.
    I had some Fuji X100S that had been sent to me for testing. These images had been adjusted so they were B&W even when delivered as RAW. COP8 was seeing that they werent correct and was crashing.
    I would have thought that it would exclude them as 'corrupt' images instead of crashing.


    A thought for the developers. If the image data doesnt parse correctly then mark the image in the browser as corrupt or unrecognised!!!


    One would have to know what to look for before being able to trap the potential problem.

    Probably best to forward the files (are an example of one of them ) to Phase for analysis so that a check can be put in place (or so that any pre-existing check can be amended).

    At least the testing has proved something!

    Perhaps in some way it validates Phase's principle of never editing a RAW file on the basis that to do so is likely to create unpredictable problems?



    Grant
    0
  • CAPTURE NIKON D700
    tray this on your Imac please !
    clean C1 Pro deinstallation and installation on your Imac :

    1. move C1 Pro folder to trash !
    2. make a copy from Capture One folder, found in user -- Library / Application support / ... and rename it
    3. open Terminal : and type sudo find / -iname "*Capture one*" -print > ~/Desktop/suche.txt
    4. in the Protokoll date on Desktop you will get all hide C1 date locations on your imac drive 😉
    5. move them all to trash 😉
    6. install C1 v8 new 😄
    7. replace only your user setting folders " LCC or Workflow ... " from the Capture One saving folder in the Original folder under user -- Library / Application support / Capture One "
    in Capture One Pro 8 setting
    make this corrections setting
    1. activate CPL function "depending on your hardware"
    2. deactivate all providers cameras and activate only the one you use like me "NIKON"
    avoid both Nikon and Canon selects 😭

    i hope you will get helpful !
    0

Post is closed for comments.