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
  • Douglas Lucock
    BeO - Unfortunately I never had a cause to review memory in v8 (and have deleted from my system now since v9.01 came out), but given that in v8 the keywording was so basic that I only used it sparingly (basically what came across from Aperture earlier this year when I switched).

    Not sure if I should open a case on this problem (speed when deleting/renaming keywords) as it may be "working as designed" (even if a poor design), plus its dificult to get the memory dump etc without cancelling the process in the middle (which i don't want to do given the stories of corruption when others have cancelled). Its likely, given that it all finishes OK after several minutes and most processes and memory are then back to normal so taking the snapshot at that point may be of little use.

    At the moment I can live with it as I only had a dozen or so renames/deletes and they are all done. (PS Boy I miss FACES functionality in Aperture...which I used extensively to catalogue/find people in photos. For now in C1, I have set up a Faces keyword with individual names as children and am just keywording the photos for those I want identificable people in)

    Overall - I can live with the anomalies for now - its still all about the image and this product with my limited ability as an keen amateur enthusiast rather than a professional gets me personally to a better image quicker.

    Doug
    0
  • BeO
    Top Commenter
    Thanks DWL.

    Your Mac is certrainly not suituable to calcualate climate changes until the end of the century, not even the weather for the next week 😉, but with a catalog of only 40.000 images I do think that 2-3 min. + 10-20 sec. unresponsiveness when renaming or deleting a keyword is actually something which should be improved,imho.

    P1 very likely might consider feedback / tickets from real world users as helpful, especially if it is a new feature as new features tend to have issues which do not occur in test systems in lab conditions or durinig beta testing.

    It is of course up to you, but I guess the only way to achieve improvements is via support tickets from concerned users, this helps them recognizing and prioritizing.

    This having said I would like to see support for Olympus OMD-EM 10 Mark II first 😊)

    cheers
    BeO
    0
  • harald_walker
    [quote="DWL" wrote:

    Not sure if I should open a case on this problem (speed when deleting/renaming keywords) as it may be "working as designed" (even if a poor design), plus its difficult to get the memory dump etc without canceling the process in the middle (which i don't want to do given the stories of corruption when others have canceled).

    Please do! How else is product management supposed to set priorities and decide to fix/improve something, if they don't receive feedback from users? I hope they sometimes look into the forums but then they should let us know that they are working on it.
    0
  • Steve Babb
    I'll also log a case. Twice c1 has stopped responding tonight. When I checked I found it was using 15gb and then 23gb ram! I was only working on three images. Never had memory issues on cp8. It seems to just keep growing. I'm using fuji raw files.

    It seemed to get really bad when I tried to edit images in silver efex.

    I'm running the latest build.

    Regards
    Steve
    0
  • Narq
    I'm running 9.0.3 and am still having problems. Memory usage isn't quite as out of control, but the app is generally unresponsive after importing my images into a catalog. I've had most "success" by leaving it alone and not clicking on "all images" in the library, but that meant that my previews weren't all generated.

    There seems to be a very serious problem in how the data is organised or accessed.

    https://pbs.twimg.com/media/CZpA01uWYAIShdj.png:large
    0
  • peter Frings
    Hi all,

    I've been trying to import my Lightroom catalog (formerly Aperture catalog) of 60K+ images for days now. C1 9.0.3 starts doing that just fine and memory footprint remains stable for a while. Then, at some point, memory footprint starts ramping up until all memory is gone, swap space is gone, and the mac suspends C1 (and then the rest of the apps as well… :-/ ).

    I tried it at my mac at work, a late 2015 iMac 27" retina with 16GB of RAM and plenty of disk space; C1 got halfway and then stalled, and so did the mac.

    UPDATE: I've been able to ingest the entire catalog by interupting the import when the memory got too high (around 40GB), restarting C1 and then importing the same catalog again, interrupting, restarting, etc. C1 is thankfully smart enough to skip the ones already imported, and that without requiring more memory. Right now, it's building the thumbnails (which will take about 9 hours), so I hope that by the time I get in tomorrow my catalog is ready to roll! Fingers crossed!

    I'm seriously doubting whether C1 9.03 can handle such large catalogs. Lightroom handles it fine, Aperture did. When you read the comments on this forum, C1 has a serious problem with memory consumption and overall performance, or is that just me interpreting the posts through my now not-so-rosy glasses? However, for fun, I tried assigning a keyword to all images in a catalog of 600 images (test version). It took more than 5 minutes! SO, I'm not looking forward to the cleaning-up I'll have to do once (if ever) the import succeeds; it seems that C1 doesn't do well with my nested keywords…

    What do you people do when having large catalogs? Are they OK once imported? If so, what's the trick to import them?

    Cheers,
    Peter.
    0
  • meanwhile
    I don't doubt Phase One's programming skills or expertise dealing with all aspects of imagery, from every angle and on every level.

    I am starting to doubt their database expertise though. It may be time to bring someone in from the outside to fix and optimise the database use in C1. It's SQLite, and lots use it, but it definitely seems to be one of the main bottlenecks and weaknesses of Capture One. Maybe you just need an index genius to come in and turbo-charge the current setup? I'm not sure, but something needs to be done.
    0

Post is closed for comments.