Memory leak still present on C1 15.3.3

kkygeek

• September 06, 2022 14:30

Closed the application after importing into a catalog, still eating memory after half an hour. If I do an end task on it, it will end up with a corrupted catalog and I need to start over. 

Nothing seems to be done about it. Should have switched to Adobe (which I don't like much), but C1 is just a mess on windows.

1

• 

  Propheticus

  • September 06, 2022 15:35
  • Edited

  That doesn't sound right. A memory leak would steadily increase mem usage while the app is running, but not keep it running after you close it.

  Are you sure the importing process (and generating previews) had already finished by the time you closed C1? Otherwise it could be a background process finishing the preview generation.
  I won't disagree C1 knows its fair share of bugs, just trying to help you troubleshoot.

  Have you tried running a catalogue integrity check /validation after doing the import before closing C1?

  (With starting over I assume you meant starting with a clean new catalogue into which you import, or do you restore/recover the same one? Perhaps worth a try creating a new clean slate and then importing from the backup of your old/current one.)

  If you tried all this already and just came to vent; yes, bugs can be frustrating and time consuming. Good luck to you trying to fix it!

  0

Post is closed for comments.