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

Import memory leak work-around for Mac

Permanently deleted user

I have a memory leak work around for Mac. I stress that this isn't a fix, but it does allow you to work around the bug.

I needed to import a 2TB Aperture library (from a decade ago) into CaptureOne 22, to access some old photographs.

The import started at great speed, self estimating 5 hours until completion, this later became 13 hours estimated. A couple of days later the import process was still less than half way, still reporting 13 hours to completion, with no apparent progress.

I suspected a memory leak:

I confirmed that if I opened lots of apps all at once, then immediately closed them all again at once, this forced C1Pro to surrender up memory. But after a while the process would grind to a near halt again. I couldn't sit there all day opening and closing Apps to force C1Pro to release memory.

I created a MacOS 'Automator' workflow script that rapidly opened Affinity Photo, Affinity Designer, Affinity Publisher etc all at once, then closed them all again. Executing this takes about 5 seconds on my M1 machine. I set this workflow to loop continuously (for 9999 minutes) running the open-close tasks every 1 minute 29 seconds. 

With the Automator script running the import cleared itself up in about half a day, making this old Aperture library available in C1Pro.

It would be great if the C1Pro developers cleaned up the leaky code. But if you need to get to an old Aperture or Lightroom library, then this may make the task possible for you.

I hope that helps.

0

Comments

5 comments

Date Votes
  • OddS.

    > Chris McCarthy: It would be great if the C1Pro developers cleaned up the leaky code

    They may not even know about it, and they do most likely never read this forum. You can only get a message through to them via the "Submit a request" at top right on this page.

    0
  • Permanently deleted user

    Thanks OddS. To be honest, I don’t think the C1P developers will be interested in fixing a bug relating to importing from Apple Aperture, because Aperture has been discontinued for so long now, most migrations will have been completed years ago. Perhaps the C1P developers will look at the memory leaks if they affect importing from Lightroom, but I don’t have Lightroom to try from. It seems that there are other image import memory leak problems in C1P generally which this work around might help with. 

    0
  • OddS.

    > Chris McCarthy: I don’t think the C1P developers will be interested in fixing a bug relating to...

    All developers/programmers I ever knew would like to locate and fix a memory leak. If not for the end user so for her-/himself to learn from. What did I screw up this time... If you found the issue in v21 or older, management would likely not allow time spent on it as a fix must be followed by a new update release of the old version. You are apparently referring to the current version, v22, there will be a next release anyway.

    The memory leak may not be isolated to Aperture imports, it may affect other functions in mysterious ways.

    I really think you should report it.

    1
  • Permanently deleted user

    Hi OddS,

    Good call. I've submitted a request, it will be interesting to see if anything comes of it.

    Cheers

    Chris

    0
  • Chelaru Ionut

    they have more memory leaks on Mac then that. This will probably not be fixed any time soon as capture one spends time and money trying to make a iPad app....

    0

Post is closed for comments.