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

Memory leak in import viewer

Sakari Puhakka

Hi

When I open import viewer it takes up sometimes all the memory up to 32 GB which I have in my Windows 10 Pro PC. I have Capture One version 21.14.2.

1

Comments

5 comments

Date Votes
  • Permanently deleted user

    Same thing happening with Mac 10.14 Mojave and Build 14.3.1.10 and 64GB of memory.  Importing 20MB Raw files you can just watch it die.  33 images 5GB, 400 images...pray they make it before C1 locks up.

    0
  • SFA

    What happens if you are also running other applications?

    Does C1 still try to use all of the available memory?

    0
  • Permanently deleted user

    Yes, I was editing today.  Killed all other apps and C1 had about 32GB of 64GB to use. Other was running background app/tasks.  Basically could watch it ramp up as the number of files were being imported. Did successfully import 400 files over 20-30 minutes. It did max out memory, but didn't hang.  The new Import review function does help when making the first cut of 500+ images.

    iMac Pro (2017), 3.2GHz Xeon W, 64GB RAM, Radeon Pro 64X 16 GB graphics card.

    Between this and trying to load 20 keywords across 300 images and having the beachball engage every time for 10-60+ seconds does get tedious.

    0
  • SFA
    • Edited

    If the process finishes and the memory is released (making allowances for some new information about the imported files being retained in anticipation that you may be about to do some editing) I would say that sound like normal usage.

    There is not much point in have a stack of memory but not making use of it when it is available.

    Your keywords issue sounds odd. I cannot recall ever having that sort of issue with keywords but we may not be using the same methods of loading them.

    Also, I use sessions. If you use catalogs there may be different factors (i.e. larger numbers of images in the database) to consider. Nevertheless, it reads like there may be some sort of underlying system challenge that should be resolvable once identified.

    The other difference is that I am using Windows so your KW performance experience and mine could be different in any case.

    0
  • Permanently deleted user

    You would think so, but it's definitely different than in past versions.  It essentially feels like C1 is not releasing memory once unused or trying to put the entire import in RAM as it incrementally writes the files into the DB.

    The keyword issue was researched with a service ticket, but has never been resolved.

    I can't imagine what it's going to be like when I move to larger RAW files.

    Onward through the fog....

    0

Post is closed for comments.