Frozen Capture One and Memory Leak
Hi, all!
I recently upgrade to 12.1(.1.7) and am having trouble opening the default database (it's big!). When I open Capture One, it takes a bit to settle down and allow me to move around within the app, but if I let it sit for more than a minute or two (switch to another app, for example), I notice my external drive stack (on which I keep my database) suddenly kick into gear and the app starts to consume memory. The application then goes to "Not Responding" and ignores all user input.
I'm letting it run now, and am seeing >62GB on a 32 GB MacBook Pro. "Yay for fast swap," and all that, but this is probably a bit much.
When I run lsof and look for files that are open on the external drive, I can see that Capture One is doing "something" to the originals and then the .cop files - I'm guessing, updating previews. Is there some way that I can control this behavior? I obviously can't buy and install more RAM. This is new behavior at this point.
While writing this, the memory use shot up to >69 GB, the drive isn't recording any read/writes, and the only file now open on the drive is the .cocatalogdb file associated with the database. Something is VERY unhappy with Capture One.
Before closing, it's consuming > 76(!) GB, is doing no I/O and only has the database file open.
Any ideas how to improve the situation? I had, over the weekend, exported the old database to this because I suspected some possible corruption that the checker didn't catch. (I can obviously restore from backup if absolutely necessary.
I recently upgrade to 12.1(.1.7) and am having trouble opening the default database (it's big!). When I open Capture One, it takes a bit to settle down and allow me to move around within the app, but if I let it sit for more than a minute or two (switch to another app, for example), I notice my external drive stack (on which I keep my database) suddenly kick into gear and the app starts to consume memory. The application then goes to "Not Responding" and ignores all user input.
I'm letting it run now, and am seeing >62GB on a 32 GB MacBook Pro. "Yay for fast swap," and all that, but this is probably a bit much.
When I run lsof and look for files that are open on the external drive, I can see that Capture One is doing "something" to the originals and then the .cop files - I'm guessing, updating previews. Is there some way that I can control this behavior? I obviously can't buy and install more RAM. This is new behavior at this point.
While writing this, the memory use shot up to >69 GB, the drive isn't recording any read/writes, and the only file now open on the drive is the .cocatalogdb file associated with the database. Something is VERY unhappy with Capture One.
Before closing, it's consuming > 76(!) GB, is doing no I/O and only has the database file open.
Any ideas how to improve the situation? I had, over the weekend, exported the old database to this because I suspected some possible corruption that the checker didn't catch. (I can obviously restore from backup if absolutely necessary.
0
-
Create a Support Case and have the C1 Support Team discuss things with you.
The Log files may be useful - they will ask for them anyway.
Grant0 -
Thanks- will do. 0
Post is closed for comments.
Comments
2 comments