Zum Hauptinhalt gehen

C1 23 has a memory leak

Kommentare

72 Kommentare

  • Offizieller Kommentar
    Jack W
    Admin

    The 16.2.2 update we released yesterday should fix this issue. You can download it here.

  • SFA
    Top Commenter

    Submit a request (captureone.com)

     

    I would suggest you use the link above to create a Support Case.

    0
  • Ray Hardy

    Same issue on the Mac Studio Ultra

    0
  • Frank Schroeter
    Moderator

    When you contact our Support, please include your Capture One logs (username/Library/Application Support/Logs), System Report (About This Mac > More Info > System Report) and Analysis of the Capture One process when it is paused due to RAM consumption (Activity Monitor > select process > select Sample Process from the three-dots-button in the top bar of Activity Monitor).

    1
  • FirstName LastName

    Same here on M1 Max with 64 GB RAM, OS 13.2.

    I was hoping build 16.1.1.16 would fix the memory issue, but same forced-quit issue happens at least 2-3 times per shoot. Capture 23 is terribly, unacceptably, unstable. 

    0
  • Help Desk

    Same here. So so painful when work stoppage is not an option.

    0
  • Andrea Thode

    OSX 12.3, Capture 16.1.0.126, still a huge problem

    3
  • Frank Schroeter
    Moderator

    Andrea Thode, you are not on the latest version of Capture One. Try updating to 16.1.1. If the problem persists, please file a support case with the details I mentioned above.

    You also want to update to at least the latest Monterey version, if not Ventura. 

    0
  • Ji���_ Kala

    I have the same problem with the latest version 16.1.1. And I have already reported it. Since 16.1.x CO1 is quite unstable.

    1
  • Konstantin Odin

    Same Issue here.

    MacBook Pro 14" M1 Pro 16GB of Ram, but 50GB+ issued by CaptureOne 16.1, 16.1.1 and 16.2. On MacBook Pro 16" and 64GB of Ram, it stays around 50GB. its super slow, but kind of usable.

    PhaseOne Support is already activated, but only asked for update and that they are not able to reproduce.

     

    1
  • FirstName LastName

    @Konstantin Odin drift hunters

    Thank you for the helpful post!

    0
  • Frank Schroeter
    Moderator

    Konstantin Odin, do you get a warning that Capture One does not react due to low memory (See screen shot further up in the thread)? If not, you have not hit the bug discussed here. Merely using 50GB out of 64GB available is not a bug per se.

    1
  • Konstantin Odin

    Frank Schroeter jupp, that it exactly the point - system out of memory.

    the other information is just an addition, that in my case, the memory is capped at around 50ish GB (I believe the max I have seen was 52GB on both mashines)

    0
  • Frank Schroeter
    Moderator

    Konstantin Odin, can you send us a Sample of the hanging Capture One process, then? That may help to identify the root cause.

    0
  • Konstantin Odin

    Frank Schroeter do you have access to Case Number: CAS-00011364 CRM:0295000000141? There are some log files and other data. I will get you a fresh sample, as soon as I got the issue again. 

    what's your preferred way of sending data to this case? Copy Paste it here or send you all the data via a transfer link?

     

    0
  • Frank Schroeter
    Moderator

    Konstantin Odin, I do not have access to Phase One support cases, as Capture One and Phase One are separate companies. But I am in contact with James, who handles your case. That said, this is unlikely to be a Phase One camera issue, we have reports from users of other cameras as well.

    The Sample file will likely be large. I suggest you upload it to a cloud service of your choice and send a link to captureonefeedback@captureone.com.

    0
  • Sebastian Zell

    Hello Community,

    same problem in our Studio.

    Different Systemversions of MacOS with M1 with newest version of Capture One 23 running full on program memory.

    I found kind a "hot fix" solution to slow the process of running full down:

    Go to settings and scale down the preview image size at least to 1024 or even to lowest 640.

    Memory is still running full, but much much slower.

    1
  • Frank Schroeter
    Moderator

    We have managed to reproduce this in-house as well now and are looking for the root cause.

    0
  • Scott Heldorf
    Since updating to the latest version (16.1.2) I have had terrible issues with CaptureOne crashing due to running out of memory.
    For context, I regularly digi-op on e-comm shoots where we might put upwards of 3000 photos throught the session with a Canon R5 shooting Raw files.
    I havent had a problem running these sessions at all previously, but now after 15 minutes or so of shooting C1 either crashes or I have to restart it to clear the memory.
    This is obviously a really frustrating process when trying to get through a lot of images in a day!
    My macbook is a 2022 14" M1 with 16GB of ram, clean install with nothing else on the system apart from C1 and Adobe Suite programs.
    I have tried removing C1 completely and reinstalling fresh, even the previous version, but today I am still having the same issue...
    I am running a memory monitor, and it sits on about 15-18% until the photos start coming into the computer, then sky-rockets to almost 100% and doesn't return unless I restart the program.

    I didn't get a chance to screenshot the crash error message today I'm afriad, but definitely sounds like it was the same as other people in this thread.
    0
  • Frank Schroeter
    Moderator

    Scott Heldorf, how does it behave when you set Preview Size to 640?

    0
  • Scott Heldorf

    Frank Schroeter, it takes a few minutes longer but ends up maxing out RAM again.

    Any update on this? This is a critical part of my business as a digital operator on set.
    I have had to uninstall C23 completely and go back to C22 now. I have a big e-comm shoot on Wednesday so I will have to cross my fingers and hope like hell it's ok.


    0
  • Frank Schroeter
    Moderator

    Scott Heldorf, initial investigation has not turned up a smoking gun. You wrote in your initial post that memory is freed after you restart the program - this is an important distinction: Is memory is freed after Capture One is quit, or only after a OS restart. Can you confirm this? What we have reproduced in-house so far is that it is freed after OS restart.

    It would be helpful to hear this from everyone affected. 

    0
  • Sebastian Zell

    Frank Schroeter, as I figuered out memory is already freed after Capture One is quit.

    I think the source of the problem are the thumbnails.
    The memory only fills up when new photos are added. When shooting is paused, the memory does not increase either.

    With the reduction of the size of the thumbnails, the problem still occurs, but not as fast.
    I think Capture One does not manage to "forget" created thumbnails.

    Similarity to the current problem is marking a folder as favorite, where the folder remains "loaded" and ready at any time.
    Could this also be the cause of the current problem, that every folder is treated like a favorite folder?

    1
  • Scott Heldorf

    Frank Schroeter, thanks for following up Frank:the memory releases as soon as Capture is closed. I dont need to restart the OS.

    0
  • Andrea Thode

    Today I ran again into the problem but I needed to hard reset (via holding the powerbutton) my MBP since capture froze the whole system.

    After that it worked fine as long as I don’t shoot a series of images.

    (Sony A7R V btw.)

     

     

    0
  • Robert Bittle

    Same issue.  On set for large fashion company and I've been limping along all week.  Very frustrating.  I have reduced the size of my previews and gone back two versions of 23.  I was using the latest version but it filled up the memory VERY FAST.  Going back to 23.16.0.2.21 seems to take longer to break down.  Also, The whole C1P system is slow, clicking populated folders or changing tool tabs gets me a spinning ball.  I have been more than impressed with C1P on my M1 up until now.  I guess the only difference is I upgraded to the latest version of Monterey 12.6.5 last weekend?  It shouldn't matter, that OS has been out for a while. 

    2021 MacBookPro 16, M1 Max, 64G ram 4TB ssd.  Monterey 12.6.5. Shooting with R5, no cards. Tethered with Area51 cable.

    Like I said before, It was working very well until upgrading to latest Monterey. 

    0
  • Frank Schroeter
    Moderator

    We are observing that a lot of RAM is consumed when tethering with Auto Sync Sidecar XMP set to Full Sync (in main menu > Settings > Image > Metadata). Does any of you guys have this setting? 

    0
  • Sebastian Zell

    Frank Schroeter Auto Sync Sidecar XMP is deactivated in my C1. Im used to have "pack as EIP" activ.

    Attached u can find my setting, may other users can compare and confirm there settings so C1-Team can use most common settings to search for the error.

    I see most are using M1 Chip with up to 32 or 64 GB.

     

    0
  • Frank Schroeter
    Moderator

    Thank you Sebastian Zell! Your reply supports the notion that we are looking at several root causes here.

    Indeed the only thing all known cases have in common is Apple Silicon. I have not heard of an affected Intel Mac.

    I encourage you to also try the current Capture One 16.2.0 Beta, which has some changes that may fix the problem you encounter, even though the one related to Auto Sync Sidecar XMP is not fixed there. 

    0
  • Sebastian Zell

    Frank Schroeter Where can I download the Beta-Version to test if the problem got fixed?

     

    Have u looked into the possible root of the problem I mentioned earlier in a comment here:

    I think the source of the problem are the thumbnails.
    The memory only fills up when new photos are added. When shooting is paused, the memory does not increase either.

    With the reduction of the size of the thumbnails, the problem still occurs, but not as fast.
    I think Capture One does not manage to "forget" created thumbnails.

    Similarity to the current problem is marking a folder as favorite, where the folder remains "loaded" and ready at any time.
    Could this also be the cause of the current problem, that every folder is treated like a favorite folder?

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.