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. ⚠️

Increasing Lag

Permanently deleted user
While working in layers everything can be fine (start of day). Brush very responsive and keeping up with the Wacom pen when using a Cintiq 27 but after an hour or so lag starts to creep in and I have to wait for C1 to catch up with the pen. Monitoring Activity monitor shows C1 gradually increasing the memory used as time goes on. Starts at 3.95GB and increases to 12-14gb. Close app and restart and it goes back to 3.95gb.

Is this normal? is there anything I can do to improve things?

System
MBP Retina, AMD Radeon R9 M370X 2048 MB, Dual Graphics Card, Intel i7 2.5ghz, 27 Inch 2540 x 1440 Cintiq or 27 2540 x 1440 standard monitor. Happens with both monitors.

All files on internal SSD drive. working in Sessions.
0

Comments

10 comments

Date Votes
  • Permanently deleted user
    Would not call it normal but I observe the same.

    There are lots of processes in C1P where used memory (both computer and GPU memory) is not (fully) released after use, not even when closing the corresponding catalog or session. C1P therefore gets slower and slower using then compressed compressed memory and eventually the Mac will run out of application memory. If latter happens during a batch process, i.e. importing, exporting, preview generation it will most likely crash.

    I am not sure whether this happens in general; I observe it on both of my Macs (iMac, Macbook). Just open and close a catalog or session several time and monitor memory via activity monitor. An empty catalog "costs" me about 1.8 GB, as session 1.6 GB. With images in it gets worse (at least 4.5 GB).

    For the time being I use only one catalog / session at a time and restart C1P once it starts using compressed memory extensively.

    PS: I have submitted bug reports for both computer as well as GPU memory usage
    0
  • Permanently deleted user
    Interesting. Sounds like the same observation.

    I didn't know whether there was a session config file somewhere that could be deleted/reset. I tried closing the session and re-opening it to see if it improves performance but C1's memory usage remained the same. I had to close it down fully to get it to reset to 2.39gb.
    0
  • Permanently deleted user
    Have not found any way to release memory besides closing C1P.

    You can crash C1P by opening and closing an empty catalog or session receptively; it depends on the memory installed how often you have to do it. If you have at least one images in it this happens much faster. Mine stalls when compressed memory is larger than twice the available RAM.
    0
  • HansB
    [quote="FL" wrote:
    Have not found any way to release memory besides closing C1P.

    You can crash C1P by opening and closing an empty catalog or session receptively; it depends on the memory installed how often you have to do it. If you have at least one images in it this happens much faster. Mine stalls when compressed memory is larger than twice the available RAM.


    Same experience on my side.

    [quote="HansB" wrote:
    ...
    When working with a number of catalogs (one at a time), I noticed that Capture one does not free up or re-use the previously used memory. After closing a catalog it just takes new memory when opening another catalog. This way, it eats up all memory, becomes unresponsive sooner or later, and finally crashes the system.

    I verified this with a new, empty catalog on two different Macbooks. There never was a single image imported, therefore not related to the Canon specific issue. CO was freshly started. With each closing and opening of the empty catalog, CO uses 1.9GB more memory.

    Support case filed, PO support verified it as a bug and reported to R&D.

    For the time being, changing catalogs means close and re-open CO.
    ...



    Regards,
    Hans
    0
  • Permanently deleted user
    When did you submit the bug?

    I submitted a similar bug on the GPU memory - here the computer does not crash but in my case exporting files takes longer and longer - beginning of Dec. 2015 but have not seen any fix yet.
    0
  • HansB
    FL,

    I submitted it about 2 1/2 weeks ago.


    Regards,
    Hans
    0
  • Permanently deleted user
    I've just sent a bug report as well. I guess the more the better as it will confirm a problem and not a one off issue.

    Edit.
    I was able to get up to 24gb of memory usage for C1 Pro9 for one active Session. Each time you open a session and close one (to leave one active) it doesn't release any memory, just keeps taking more and more each time you open a session and doesn't take into account that you've closed one and that it can release that memory back to the system.
    0
  • Peter Orczykowski
    Without sounding too pessimistic... This issue pops up from time to time. I can vouch for at least three major (paid) releases. I have also submitted support case etc. Nothing is going to happen if the past is any indication for the future. I refuse to get used to it, but for now I am dealing with it by regularly closing and re-opening C1. In a 60K image catalogue this is a 5 minute coffee break. So much for a modern, 21st century software ☹️
    0
  • nigel turley
    I logged a call on the same subject in early January and this was tech support's reply:

    Hi,
    I have logged all this with a few other cases into an indepth report called CO-9184 if you get in touch about it again quote this number.
    Hopefully our development team will be able to shed some light on the issue.
    Kind regards
    Phase One Support

    So, an 'indepth report' exists and I'm guessing anyone can refer to it when requesting updates...
    0
  • Mispel3991
    Of course it's not the solution to the problem , but to free memory I use Memory Clean. For me it works fine and you can always give it a try. To be downloaded for free from the App store or from .
    0

Post is closed for comments.