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 9 memory leak building thumbnails and crashes

CatOne
Hi,

I tried Capture One 8.x and really liked the results I got from it, but the cataloging and performance had too many issues for me to use it to replace Lightroom.

So with 9 being released, I was excited.

I first tried on my laptop where I have about 5000 images in Lightroom. I imported the catalog to CO 9 and that worked OK. But at building preview 1777 out of 5000 images, I got an OS X popup saying my Mac was "out of application memory." This is odd as this is a new MacBook Pro with 16 GB of RAM. So I checked and CO was using 78 GB of RAM. 78 Gigabytes! It appears there's a very big memory leak with preview generation.

I then tried on my desktop iMac (Retina 5K late 2014). It has 32 GB of RAM. I imported my LR catalog (44,000 images on this machine), and after about 20,000 images the preview generation started. RAM usage went up to 50 GB. I hit command-Q to quite Capture One and got a dialog "do you want to quit while an import is in progress?" and then got an immediate crash. Upon restart of CO, I got a "your catalog may be corrupt" message, and when I tried to fix it, I got an "ERROR: Cannot connect to database."

So I guess I've found a HUGE memory leak, a few crashers, loss of a catalog, and some other things. Did anyone test LR catalog import, or preview generation with more than 1000 images? I really WANT to like Capture One, and really want to give it a fair shake, but I'd have a tough time wanting to spend $300 on something that can't even generate 2000 previews before blowing up; I can shoot this many images in a day ☹️
0

Comments

67 comments

Date Votes
  • Andriy.Okhrimets
    Just suggesting a perfect workaround which does decent job for me when working with C1 and CANON files.
    sudo purge Gives a decent memory cleanup to allow my Mac to continue operation.
    Other idea is to install free memory cleaner from apple store which will do the same work automatically for you instead.
    Using this tools I was able to get a manageable performance on import of 5K+ of Canon images, on 8GB machine mac.
    0
  • Badunit
    Add me to the list. My catalog is 30K+ images, about 25% are Canon raw files. I was regenerating previews, Capture One got to nearly 70GB of memory usage(!!!), I got the "out of application memory" error message, and Capture One was no longer responding. Had to Force Quit. I assume I'll have to repair my catalog again. This is my first day with the trial of Version 9. Not going well so far.
    0
  • Smogg
    I imported(auto-level applied) 12k images into new catalog(NO Canon-files, only tiff files from epson scanner, corrected in Photoshop, sRGB-profiles). After 20-30 min active browsing these files C1Pro consumes huge amount of memory and continually freezes with system notification: "out of memory"

    I have iMac 4 GHz Intel Core i7 with 32 GB(!!!) installed
    0
  • twelvefingerjoe
    @ problems with canon sdk
    [quote="Christian Gruner" wrote:
    I am aware of that, and our Support Team have been notified of the real cause.
    I cannot comment on specifics for the service release, but it won't be long.

    but what is the conclusion? don't use C1 v9 with canon?
    and what is a R&D employee
    0
  • Michael Sonshine
    [quote="twelvefingerjoe" wrote:
    @ problems with canon sdk
    what is a R&D employee

    R&D means Research and Development.

    He is probably one of the technical staff. Probably a software engineer or architect or some other technical member of the team.
    0
  • Christian Gruner
    [quote="MikeFromMesa" wrote:
    [quote="twelvefingerjoe" wrote:
    @ problems with canon sdk
    what is a R&D employee

    R&D means Research and Development.

    He is probably one of the technical staff. Probably a software engineer or architect or some other technical member of the team.


    Close enough 😉
    0
  • twelvefingerjoe
    [quote="Christian Gruner" wrote:
    Close enough

    So it's Imagineer then.
    0
  • Badunit
    Is there a way to cancel preview generation? It was somewhat usable when it was generating a few hundred previews at a time as I browsed my images but, unfortunately, I asked it to regenerate all previews and it has been a mess ever since. When I am able to finally get my catalog open again, it starts right back generating previews and eating memory. Is there a way to stop it? I am using a Mac Pro running El Capitan.
    0
  • Michael Sonshine
    [quote="Christian Gruner" wrote:

    Close enough 😉

    Ah. Typical of me. I read only that part of the post that initially caught my eye. Let me revise that answer:

    He is probably one of the technical staff. Probably a test engineer.

    That should do it.
    0
  • Narq
    Same thing here, MacBook Pro (Retina, 15-inch, Mid 2015), 16GB Ram, Canon 5DIII raw files in sessions with around 1000 shots per session. Ran out of memory and the system stopped working properly. Left it for a while, the beach ball disapeared, and it worked again although memory usage was up to 20+GB. At 50GB the system hanged completely and had to be shutdown by holding the power button. Hoping for an update soon, but like the sound of sudo purge until then, hopefully I won't have to go back to C18 and loose my adjustments.

    C18 has a nag screen that tells me to upgrade to C19. It would have been nice if that same mechanism could have told me there was a known issue with my configuration, but I guess then they'd have to start making suggestions about what to do while we await the update. I'd suffered a few crashes before I googled it.
    0
  • Badunit
    Well, never mind on how to stop it from processing previews. Capture One now says my catalog is "not recognized" and that's that. If I had been using Capture One for a while, not just the first day of a trial period, I would be extremely unhappy with that turn of events.
    0
  • Andriy.Okhrimets
    Need to restore catalog file from a backup. It looks like your catalog file is screw up.
    0
  • Aaron M
    Hi Badunit, your catalog probably got corrupt from having to force quit Capture One when it crashes. Happened to me, too. And also some other people on the forum...

    There is a way to repair the corrupt catalog file, but Phase One technical support is unwilling to help. Instead, I found someone online was able to fix mine and restore all of the adjustments I made (although I did pay him a little money).
    0
  • BeO
    Top Commenter
    Hi Aaron,

    can you pay him another beer and get the recipe how to repair it so you can share it here... 😊 😄 😕

    Could maybe even become a sticky post or into some FAQ section..

    cheerio
    BeO
    0
  • Permanently deleted user
    Have posted this for another person who had the same problems:
    I managed to "recover" a destroyed catalogue by simply creating a new one and importing the old damaged one.

    Dear Phase One - with all due respect for the great work on this software. Maybe it is time to make a public announcement that Capture One 9 is at present NOT working reliably with Canon files.

    A pretty serious issue that would affect one or two photographer out there.
    0
  • Aaron M
    Yes, might want to try BerndInBerlin's solution first. Could be easier. I have no idea how my guy fixed it. He ran it through some of his special software or something. 😊
    0
  • HansB
    Rebuilding is also possible from command line. I don't have a broken catalog to test it, but maybe somebody wants to try it on a copy of a broken one? It's command line, so cd into the catalog file.


    cd <YOUR>.cocatalog
    mv <YOUR>.cocatalogdb <YOUR>.cocatalogdb.yourbak
    echo .dump | sqlite3 <YOUR>.cocatalogdb.yourbak | sqlite3 <YOUR>.cocatalogdb


    Another option might be to query VACUUM; on the catalog database.

    Not sure if this works, but maybe it helps creating a solution.


    Regards,
    Hans
    0
  • Paulo S. Toureiro
    Any word on if the latest patch has fixed this?
    Patch notes were a tad ambiguous
    0
  • Smogg
    much better memory management after patch, but still not perfect with large number tiff-files
    0
  • harald_walker
    [quote="Smogg" wrote:
    much better memory management after patch, but still not perfect with large number tiff-files


    I've seen large memory usage when working with keywords but not a memory leak. Once the process is ready, memory usage goes down again. The problem 9.0 had was a memory leak that eventually leaves no other option than to kill the application or hard reboot the computer, often leaving a corrupt database behind.
    But a problem is still, that some actions can take a very long time and can't be canceled. I've been staring at a not responding C1 several times yesterday. It is tempting then to force quit the application but that would always risk a damage of the database.
    0
  • NNN635158767546269381
    works great here.

    RAWs from EOS 450D, 550D, EOS 5D Mark II and EOS 5D Mark III. About 80k pictures.

    I even noticed some speed up in the latest 9.0.1 when switching images.

    Hopefully, your issues will be fixed in upcoming release.

    [quote="BerndInBerlin" wrote:
    Have posted this for another person who had the same problems:
    I managed to "recover" a destroyed catalogue by simply creating a new one and importing the old damaged one.

    Dear Phase One - with all due respect for the great work on this software. Maybe it is time to make a public announcement that Capture One 9 is at present NOT working reliably with Canon files.

    A pretty serious issue that would affect one or two photographer out there.
    0
  • NN635115164314618060UL
    Still problems here after even after updating to 9.01 especially with anything to do with keywords. Cannot delete or move old keywords or it stops for ages not responding and if you kill it, yet another corrupt database. Love the way the keywords have been implemented but very frustrating when you can't do anything other than add new ones.
    0
  • NNN635158767546269381
    [quote="BerndInBerlin" wrote:
    Have posted this for another person who had the same problems:
    I managed to "recover" a destroyed catalogue by simply creating a new one and importing the old damaged one.

    Dear Phase One - with all due respect for the great work on this software. Maybe it is time to make a public announcement that Capture One 9 is at present NOT working reliably with Canon files.

    A pretty serious issue that would affect one or two photographer out there.


    Indeed, C1P seens to leak memory. I opened my catalog twice while keeping the app runing. The second time, just after the catalog have been opened, C1P needed twice a memory as the first time.

    PhaseOne: C1P features are great, now fix 😊

    Have a nice day
    0
  • BobRockefeller
    CO9 doesn't so much leak memory, for me, as it hogs it. 8GB for CO9, 642MB for Lr.
    0
  • paintbox
    Using around 22gb on my machine.
    0
  • harald_walker
    Almost 21GB (on a machine with 16 GB RAM), my new record after importing an 8K aperture library obviously caused by preview generation process.

    https://dl.dropboxusercontent.com/u/975141/captureone9-21GB.png
    0
  • Bill Wernet
    I am seeing this same sort of excessive memory usage. 20 GB and above at times.

    Help please.
    0
  • Douglas Lucock
    I had posted (and had support case) with keywords causing crash in v9.00. That was fixed in v9.01(thank you C1...great job), but similar to an earlier post in this thread, whilst its now stable (aka not crashing when mucking around with keywords), I have noticed that it takes an inordinately long time to rename or delete a keyword. On my 40,000 image catalogue (on internal 1TB SSD on late 2013 Macbook Pro 16GB RAM i7, with all images referenced on USB 3 external 2TB Lacie HDD), it can take up to 2-3 minutes sometimes to rename a keyword in the Keyword Library. Everything else seems fast and responsive , but you are locked out whilst the rename or delete completes.

    The memory starts to climb and the rainbow ball spins (almost like its just slow at checking every entry in the catalogue to see if its affected (my guess ...not necessarily fact based)). It does however if left alone, complete, and everything drops back to normal levels (CPU usage, memory etc). The very next thing you touch in relation to keywords also then takes 10-20 seconds, but after that, its back to lightning fast. Eg adding new keywords and keywording images by clicking on key words in the keyword library against highlighted(selected) images in the browser has no measurable delay. All good ....all very fast. But something crazy is happening re deletes and renames of keywords.
    Doug
    0
  • BeO
    Top Commenter
    I would assume the keywords are stored in the catalog and should be possble to work with keywords without the referenced images attached via the external drive. Does this make a difference?

    Given that the keyword tool is brandnew / revised I further assume that there might be inefficiencies which P1 will improve in a minor update, if users report their problems (which you did :thumbs up:)

    Apart from keywording, did you notice higher memory consumption compared to v8?

    cheers
    BeO
    0
  • harald_walker
    [quote="BeO" wrote:
    I would assume the keywords are stored in the catalog and should be possble to work with keywords without the referenced images attached via the external drive. Does this make a difference?

    The slowness is only due to the database in the catalog and the inefficient way how keywords are being handled in the database. If you have 40.000 images in the collection and rename or delete a keyword in the keyword library, it seems to read the keywords of each image individually from the database and update the keywords for that image if necessary. Obviously it uses some memory each time for an image version and its data and only releases that memory again when the full process has finished. These problems are solvable with a better architecture and I hope that they do something about it soon.
    0

Post is closed for comments.