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 One is crashing on me more regularly. Anyone else?

Anthony Sbarro
I have a 2017 iMac on Sierra version 10.12.6.
3.4 Ghz i5. 48 GB 2400Mhz DDR4. Radeon Pro 570 4096 MB.
Capture One Build 10.1.2.26
Fuji XT2. Lexar 2000x 32GB

I typically create a session, import photos, rank the photos, edit my favs, move them to Selects, export the photos. My files live in iCloud Drive.

It seems that the crashes are happening more frequently. The other day I was trying to open a session and CO crashed on me many times until I just deleted to Session from my computer and started over. Just now it crashed as I was cropping a photo. It has crashed for a variety of reasons at least once per session for the past few months that I've been using it (I'm still pretty new).

Also, as I move through my photos in the browser, it seems like it takes the images a little longer to render than I would think on a brand new computer - 2-4 seconds. CO tends to keep up to 2 images in cache for a minute or so then dumps the preview to render it again.

Update: It usually crashes when I quit the program. I'm going to start saving my crash reports.
At this time, I can't really adjust white balance in real time. It takes 5 seconds for the adjustment to take effect. Activity Monitor says CO is using 1.97 GB of memory. I don't really have any other programs running (Safari and Mail). I'll reboot my computer to see if that helps.
0

Comments

9 comments

Date Votes
  • Chad Dahlquist
    yup having a lot multiple times a day ?

    basically latest OS on mac and latest C1 version
    my files are all local 😊 but also I need to replace my puter 😉
    0
  • Michael Zeldin
    My system is similar to yours and I use C1 without crashes. Apple's iCloud drive allows storage and "access". Only Apple's applications are built to allow rapid and dynamic retrieval of data and those applications that do are not at all as demanding as C1. My guess this is the cause of your pain. I suggest you try to use either the internal hard drive for C1 files or deploy an extrenal drive to test this guess. C1 is not built to use a storage site like i Cloud Drive.
    0
  • Benjamin Liddle
    Best option here is to create a tech support case (via the link in my profile) and send us your log files, which can be generated via Scripts > File Packager.
    0
  • NNN636448225950231576
    Hi,
    I just had 5 crashes in the last hour. With or without GPU enabled (Windows 10, Dell XPS 9560, 4K screen)

    Still evaluating the software but this does not look good (LR is slow but crashes rarely, ACDsee has not crashed on me yet).

    This is sad as C1 looks like a fast runner with lots possibilities and excellent support for Sony cameras. But it just won't work more than 5 minutes in a row at this point (worked ok for about 2 hours). Could be heat related but CPU is not running hot.

    Puzzled and disappointed at this time.

    BTW: I already provided all crash reports so far, if that's any help. Looks like it is happening whenever I get near the "details" mode (sharpening / noise reduction ).

    Patrick
    0
  • Ian Wilson
    Moderator
    Top Commenter
    I notice you are on Windows, but this is the Mac board. See the Windows board - are you on the Windows Fall Creator's update which seems to cause a problem?

    Ian
    0
  • TonyBramley
    This has been a big problem for some time and needs to still be fixed by C1P. If you use a core analysing app you will see that C1P is chugging away at full pelt most of the time on all cores. Latest Adobe CC 18 seem to have sorted out this but C1P still needs to get this sorted particularly when rendering in HQ.
    0
  • NNN636448225950231576
    [quote="Ian3" wrote:
    I notice you are on Windows, but this is the Mac board. See the Windows board - are you on the Windows Fall Creator's update which seems to cause a problem?

    Ian


    Yes, I noticed this only later. But no: not on Creator's Update edition. Just a straight Windows 10 build 10.15063. Standard stuff 😉
    0
  • Christian Gruner
    [quote="TonyBramley" wrote:
    This has been a big problem for some time and needs to still be fixed by C1P. If you use a core analysing app you will see that C1P is chugging away at full pelt most of the time on all cores. Latest Adobe CC 18 seem to have sorted out this but C1P still needs to get this sorted particularly when rendering in HQ.


    So you are basically saying don’t parallelize the code? CO will use what is available to it, anything else would affect performance.
    If you see the opposite in other softwares (single core usage), it means that the code wasn’t optimized to multi-core processors, and performance will be way less than it could be.
    0
  • craig stodola
    [quote="TonyBramley" wrote:
    This has been a big problem for some time and needs to still be fixed by C1P. If you use a core analysing app you will see that C1P is chugging away at full pelt most of the time on all cores. Latest Adobe CC 18 seem to have sorted out this but C1P still needs to get this sorted particularly when rendering in HQ.



    If Capture One Pro is using more cores at full tilt most of the time, and Adobe is using only 1 or 2 cores at full tilt most of the time, it means Capture One Pro is more core efficient than Adobe Lightroom.
    0

Post is closed for comments.

Didn't find what you were looking for?

New post