Capture One 16.2 hogging memory until it crashes

I've been updating old sessions (going back more than 10 years) to both ver 16.2 and the current processing engine. I've been updating the sessions one after another without problem until today, when it started crashing. I've opened up the Activity Monitor and see that as I move from one session to the next, Capture One has accumulated memory usage until there is none left and it freezes. (I have 16 GB.) Is there a way to purge that RAM? Or does having it accumulate mean that it is still processing the update of a session even after I've closed, and I should let it sit?

Jim Schaefer

Kommentare