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
  • Permanently deleted user
    I have managed to build a catalog of 120K images (not in one go but in stages of 5K-10K images each time) with Beta3 of COP9.
    I havent experienced this on my MacMini or MacPro (both with 16GB RAM). Getting to 120K images and a full 'all my images' catalog in one place is a new and wonderful experience for me.

    I hope you can get a resolution to this.
    0
  • CatOne
    Well that's encouraging!

    Given I'm trying to migrate a catalog (with a bunch of metadata) from Lightroom I don't know how to do it in steps.

    It really seems like the issue is with preview generation: Memory usage while the catalog is imported is relatively stable, but once the preview generation starts, memory usage goes through the roof.

    Maybe I'll leave it hidden in the background and see if I can avoid any preview generation before the import finishes (it takes a few hours on my iMac, or at least it looks like it's going to take that long). I'm on OS X 10.11.1 at the moment.
    0
  • meanwhile
    Is 10.11.2 out yet? Perhaps give that a go, I find it more stable than 10.11.1.

    Ah, see it's not yet, beta 5 just released to public.

    Is the preview generation still continuing, or stalled? It does take a while, especially if you are generating large previews.
    0
  • CatOne
    Preview generation stops once Phase One runs the Mac out of memory. At that point, OS X freezes the process as it's a runaway and is compromising the stability of the system.

    I managed to get around the issue for now. What I was doing was starting the catalog import, and then while that was taking place, I'd navigate to a folder with photos. That would start the preview generation, which is a road to doom.

    So I just deleted the catalog and started again, and let it run WITHOUT TOUCHING ANYTHING. Then the import would complete OK (on both machines). Preview generation STILL has a big memory leak, but when memory usage gets up to 40 GB of RAM, I just quit C1. Preview generation is an interruptible background task so this can be done, and it can be resumed.

    It's still a huge programming gaffe to make it necessary to restart C1 9 every 15 minutes while previews are rebuilding. But it's better than corrupting the catalog 😂
    0
  • CatOne
    FWIW, the output from "leaks" after about 3 minutes of runtime:

    werdna:~ blloyd$ leaks 5734
    Process: Capture One 9 [5734]
    Path: /Applications/Capture One 9.app/Contents/MacOS/Capture One 9
    Load Address: 0x1079b4000
    Identifier: com.phaseone.captureone9
    Version: 9.0.0.110 (9.0.0.110)
    Code Type: X86-64
    Parent Process: ??? [1]

    Date/Time: 2015-11-30 19:09:36.242 -0800
    Launch Time: 2015-11-30 19:06:18.850 -0800
    OS Version: Mac OS X 10.11.2 (15C49)
    Report Version: 7
    Analysis Tool: /Applications/Xcode.app/Contents/Developer/usr/bin/leaks
    Analysis Tool Version: Xcode 7.1.1 (7B1005)
    ----

    leaks Report Version: 2.0
    Process 5734: 1475304 nodes malloced for 17541411 KB
    Failed to map remote region: [0x7fffffe2c000-0x7fffffe2d000] r-x shared memory (1 page) [root] (error: 1)
    Process 5734: 29326 leaks for 8147602640 total leaked bytes.
    Leak: 0x34b04f000 size=38305792 zone: DefaultMallocZone_0x10841c000

    Look at the number of leaked bytes. LOL.
    0
  • Peter Orczykowski
    I don't think this is an isolated issue and I am afraid it has been showing its ugly face in ver 8 as well. You need to raise tech support case. Try exporting/processing a large number of images, say 200+. ( RAW to jpeg conversion will do). It starts off flying and soon slows down to a trickle. I tried once 400+ images and aborted the process after more than 10 hours. The same goes for developing images - system starts with perfect, instant and real time responsiveness only to slow down to almost unusable after few hours. (You drag a slider and wait for it to catch up with the cursor, really?) This happens on both of my systems, specs almost identical to yours.

    Exiting and reloading C1 fixes the problem for a while, just like in your case. I have started support case, but suggestions were directed at my system rather than acknowledgement that there is an issue with the software. Looks like a problem they can't easily fix, otherwise they would have done it already.
    0
  • harald_walker
    Just a though.... are the results the same with OpenCL enabled / disabled for processing?
    With version 8 I have imported many Aperture libraries of 5 - 10K images without problems like running out of memory and OpenCL for processing is set to auto.
    0
  • bdacus
    [quote="harald_walker" wrote:
    Just a though.... are the results the same with OpenCL enabled / disabled for processing?
    With version 8 I have imported many Aperture libraries of 5 - 10K images without problems like running out of memory and OpenCL for processing is set to auto.


    Agreed OpenCL set to 'Never' works better for overall performance in mac.
    0
  • CatOne
    This happened to me with OpenCL turned off.

    It still happens with OpenCL turns on.

    Turning OpenCL off by default is the wrong approach.
    0
  • pjmitchell
    This happened to me as well. Tried import of an Aperture library with 4900 images and while it was generating the previews it froze with the application out of memory warning. Checked and it was at 66GB. Had to force quit.

    When I restarted Capture One 9 it continued generating the previews and managed to complete without running out of memory. Memory use climbed to about 5.5GB, but no crash this time.

    Peter
    0
  • Permanently deleted user
    [quote="CatOne" wrote:
    Well that's encouraging!

    Given I'm trying to migrate a catalog (with a bunch of metadata) from Lightroom I don't know how to do it in steps.

    It really seems like the issue is with preview generation: Memory usage while the catalog is imported is relatively stable, but once the preview generation starts, memory usage goes through the roof.

    Maybe I'll leave it hidden in the background and see if I can avoid any preview generation before the import finishes (it takes a few hours on my iMac, or at least it looks like it's going to take that long). I'm on OS X 10.11.1 at the moment.



    This is what I was finding with earlier versions in v7, v8.

    My images are stored in a file system hierarchy.
    Photos, By camera, by month, by job.

    I tried a high level import of all. That failed.
    I then went by camera from Nikon D1 through all my various cameras to current time.
    COP9 is clever enough to build the hierarchy or you can force it by doing it by camera.
    It doesnt understand if you have a large number of sub-directories in a camera folder. So I do an Add Directory. Then quit the process after addition of the directory or directories. When all are added for a camera I then click the hierarchy tree in a suitable place and do a Synchronise.
    This adds all the images in the folder BUT it misses any sub-folders (so make sure you build the hierarchy fully) ☹️

    Then when all are Synchronised you save the catalog using the Save As command. Then copy that catalog to a safe place so you have a backup.
    Voila you have a full catalog. All bit kludgy. Yes, but it works.

    The downside is that you have a catalog that take 30-50 seconds to load depending on your machine and its RAM. I am sure that PhaseOne will speed up and optimise this process as in truth if Adobe can then PhaseOne can. They are both using the same technology in Catalogs in COP and LR.
    0
  • BeO
    Top Commenter
    [quote="NNN635397989495214331" wrote:

    Exiting and reloading C1 fixes the problem for a while, just like in your case. I have started support case, but suggestions were directed at my system rather than acknowledgement that there is an issue with the software. Looks like a problem they can't easily fix, otherwise they would have done it already.


    I am a Windows user and wanted to know if you Mac guys also have issues with C1 9, as I wanted to know if maybe C1 is optimized for one or the other operating system.

    Memory leakage, the longer C1 runs, seems to be a problem with either version, Mac and Windows. My issue is with processing RAW to jpg, but not reliably reproducible. My workaround is closing C1 once in a while.

    Thanks,
    BeO
    0
  • dredlew
    Very reminiscent of v8 with the performance issues, for which I created a couple of support cases. Seems like they still haven't fixed these issues, which is sad. I liked C1's quality but the performance and workflow issues just make it a no-go for me. Lightroom's far from perfect but at least it's manageable. I guess I'll check back at version 10...
    0
  • NN635410350578640000UL
    Hi,

    i have the exact same issue here. Possible that my machine is not up to date, but with 8 it worked really well. Anyways, when i look for the memory usage in the Activity Monitor, it seams like, the the used RAM is not given free after the previews are created.
    I tried to create the previews folder by folder (this also works), but when the preview building is done, the used RAM size didn't decrease. Seams really strange for me and at the moment this keeps me from updating my license. It was so far yesterday, that i couldn`t open my before imported catalogue after i forced quit C1. It was simply just damaged.
    Really bad!!!
    0
  • Paulo S. Toureiro
    Experiencing the exact same problem on Windows 10. C1 8 ran perfectly, nothing has changed on my system other than upgrading from C1 8 to C1 9.
    Last problem I had with C1 8 was a problem with not being able to rearrange tools or drag and drop images into folders. Opening a ticket about that problem also only led to pointing out possible system problems.
    The only acknowledgement I got was in the patch notes of an update that addressed the very issues I was experiencing, I don't expect them to handle this problem any differently. I just hope that it gets resolved sooner rather than later.
    0
  • paintbox
    [quote="NNN635397989495214331" wrote:

    I have started support case, but suggestions were directed at my system rather than acknowledgement that there is an issue with the software. Looks like a problem they can't easily fix, otherwise they would have done it already.


    This!
    I upgraded my entire system to try and get C1's catalog working properly only to be disappointed.
    My last support case was deemed "closed" after no resolution. (And after I spent a lot of $$ and time on the issue)
    They should either fix the catalog or fix Media Pro so it works seamlessly with C1.
    0
  • Permanently deleted user
    I just ran into the same problem with catastrophic results. Have been working with a large, about 33000 images from a Canon 5D Mark III and kept running into the out of application memory problem. Finally it seems to have corrupted the catalogue to the point that it can not be repaired nor opened any more and many hours of editing work are lost.
    Any suggestions here what can be done? I kind of feel that a buggy product was released and professional and paying users are working as beta testers. 😡
    0
  • Michael Sonshine
    I have seen a continuing problem with memory leaks using C1-9. I am using a Mini (i7 chip, 16GB RAM, 256GB ssd, El Capitan) and found that even importing a relatively small number of images into a new catalog (100-250 Canon raw images) often leaves my free memory down around 1 GB. Exiting C1 and restarting then gives me about 7-8GB of free memory. Apparently the import/catalog create/thumbnail build is leaking memory like crazy.

    But, as I said, exiting and restarting solves the problem. A pain, but what can you do??? I have also had a problem with OpenCL on the Mini (no separate memory card, Intel Iris Graphics) and have had to turn OpenCL off for both Display and Processing to avoid getting black thumbnails (Display) or black processed jpgs (Process).

    I never saw either of these problems with C1-8. Perhaps the two issues (memory leak, black images) are related, perhaps not.
    0
  • Permanently deleted user
    According to the support team the problem of the memory leak is caused by the Canon SDK profile.
    Whoever really is to blame - I feel Capture One 9 should have not been released with such a massive bug.
    At present I use it for a few images, check with a software occasionally if I am running out of memory, close the application and restart.
    An export of a larger number, and that means something of a few hundred images crashes the program and so on.
    It's buggy and basically useless.

    So in case one has the same problems this seems to be the only way to go.

    And in case anybody has the same problem with a destroyed catalogue that can not be opened any more: Creating a new one and importing the old damaged one worked for me after many frustrating hours. Maybe this can help someone else here.
    0
  • Michael Sonshine
    [quote="BerndInBerlin" wrote:
    According to the support team the problem of the memory leak is caused by the Canon SDK profile.
    ...
    I feel Capture One 9 should have not been released with such a massive bug.

    Well, I have to disagree with that statement.

    If the memory leak really does stem from the Canon SDK there is no way C1 could force Canon to fix the problem. Your statement really means that Canon should be able to control the CaptureOne release schedule and, if Canon refused to fix the problem, they should shut down CaptureOne as a software product.

    I use Canon so this affects me directly, but I do not believe that Canon, if they are at fault, should be able to force PhaseOne to stop marketing its product and thus affect all of those using Nikons, Sonys, PhaseOne and other cameras.
    0
  • Christian Gruner
    [quote="BerndInBerlin" wrote:
    the memory leak is caused by the Canon SDK profile


    The error is not caused by the SDK, but in mechanism to read the Canon raw-files. The speed of this mechanism has been greatly improved for CO9 (up to 10x depending on the number of physical cores), but unfortunately a bug sneaked in.
    This bug will be fixed in an upcoming service-release.
    0
  • Permanently deleted user
    The information regarding the Canon SDK was provided by the support team after I had started a support case.

    When can we expect a working version? At present I do not dare to process anything with the software any more.
    0
  • Christian Gruner
    [quote="BerndInBerlin" wrote:
    The information regarding the Canon SDK was provided by the support team after I had started a support case.

    When can we expect a working version? At present I do not dare to process anything with the software any more.


    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.
    0
  • HansB
    [quote="Christian Gruner" wrote:
    ...

    The error is not caused by the SDK, but in mechanism to read the Canon raw-files. The speed of this mechanism has been greatly improved for CO9 (up to 10x depending on the number of physical cores), but unfortunately a bug sneaked in.
    This bug will be fixed in an upcoming service-release.

    Christian,

    Thanks for sharing this. I wanted to file a support case, but I'll just wait and look forward to this service release. I use Canon, and I like the changes, fixes and new things in v9.


    Regards,
    Hans
    0
  • Anne-Line Biberg
    Thanks for sharing. We are experiencing the same problem with Canon/CO9 and I checked the forum first to see if others are having the same problem. So now we´ll just wait for a fix/update instead of filing a support case. Work fast!
    0
  • Anne-Line Biberg
    Thanks for sharing. We are experiencing the same problem with Canon/CO9 and I checked the forum first to see if others are having the same problem. So now we´ll just wait for a fix/update instead of filing a support case. Work fast!
    0
  • Michael Sonshine
    [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.

    This forces me to ask a question. Since C1-9 is difficult for those of us using Canon raw files to use and test and since the trial period will be over soon, is there any chance that we can get an extension of the 30 day trial period so we can actually test the new version when it is released? Or will it also come with its own 30 day trial?
    0
  • Adrian Besoi
    The same happened to me twice already on a 30K plus image catalog and after upgrading to Capture One 9 and El Capitan. I have same spec MacBook Pro and around 1700 image the system halted and asked me to force quit the app. The system activity monitor was showing Capture One using 56GB of memory. Capure One 8 never had a problem.
    0
  • Christian Gruner
    [quote="MikeFromMesa" wrote:
    [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.

    This forces me to ask a question. Since C1-9 is difficult for those of us using Canon raw files to use and test and since the trial period will be over soon, is there any chance that we can get an extension of the 30 day trial period so we can actually test the new version when it is released? Or will it also come with its own 30 day trial?


    That is not up to me to decide. I am an R&D employee.
    0
  • Michael Sonshine
    [quote="Christian Gruner" wrote:
    [quote="MikeFromMesa" wrote:

    That is not up to me to decide. I am an R&D employee.

    I was not suggesting it was your decision. Only that you might know. I understand such things are frequency and length of trial periods are up to the marketing folks, not the engineers.
    0

Post is closed for comments.