Capture One 9.0.3 hogging CPU when openning existing session
The session has about 400 Canon 1 DX raw files in it, all in capture folder. Each time I open the session, all 4 CPU cores go to 100% and stay there for 4-5 minutes. Is there a simple way to fix this? - Thank you. Andrei
0
-
Here's more information: It does not happen with other similar sessions. After I ran "File / Verify Canalog or Session" tool, it stopped happening! (good news) Though during session verification, no errors were found. 0 -
Have all the previews been built and still CPU is used to 100% when you again open the session? 0 -
[quote="BeO" wrote:
Have all the previews been built and still CPU is used to 100% when you again open the session?
Yes, all the previews have been built... It happened to me again just now. I will describe how to reproduce it.
I imported about 1500 1DX images to new session, waited until all the previews have been built, and started going through pictures, deleting some, putting asterisks on others, nothing more. I was half way through, when I noticed C1 memory utilization was too high, 14Gb. It was around 4Gb when I started (after previews were built). Memory leak?
So I closed it to make it easy on memory. Sure, after I restarted C1, it went through the whole cycle of building the previews again. Without saying so, and that's about 15 minutes on my PC. I could continue working, but I thought it was a one-time deal to build the previews. Also, if there is a background process, it would be nice to have a way to bring that little window "Activities" and see what is going on, how much is done, how much is left to do, not just a rotating snowflake.0 -
OK. I went through them pics, then I moved the ones that has no stars to trash.
Then I right clicked on the trash folder, to bring the menu and selected "Empty Trash Folder".
The trash folder has been emptied right away.
But than there was a big surprise: it stated to re-generate the previews again, and was sitting there for like 5 minutes. By the number of the images, these were the previews of the images, that were in the trash folder, the ones that have been deleted. They are no longer on disk, maybe still in memory ? This must be a bug.
It happens, I noticed, most often with regular sessions, containing 1000+ images. It does not happen with toy sessions (less than 100 images). I think this is why it got into productions bypassing all the testing...0
Post is closed for comments.
Comments
4 comments