Memory leak? Memory use in 9.1.1
Anyone else notice that the longer you work in a Session, the more memory C1 (9.1.1) will use?
Once I find changing between file selections starts to lag, I quit Capture One and start it again.
Task Manager shows it using over 4GB of RAM usually.
I have a 16GB Surface Book, but eventually I can run into a situation where Windows 10 asks me to close applications.
And then the Compressed Memory task runs for a while after closing Capture One.
Nothing seems to trigger it directly (it's happened in Sessions with only JPG or CR2 files). It can be a session with a hundred or couple thousand pictures. It just seems like the time spent using C1 is the issue.
TTFN
Once I find changing between file selections starts to lag, I quit Capture One and start it again.
Task Manager shows it using over 4GB of RAM usually.
I have a 16GB Surface Book, but eventually I can run into a situation where Windows 10 asks me to close applications.
And then the Compressed Memory task runs for a while after closing Capture One.
Nothing seems to trigger it directly (it's happened in Sessions with only JPG or CR2 files). It can be a session with a hundred or couple thousand pictures. It just seems like the time spent using C1 is the issue.
TTFN
0
-
hello gregger,
You are not alone.
I notice this issue since the version 8, and it was worsen since the version 9.0.
As I did, you probably notice a degradation of C1 performance with the rise of the amount of memory use.
I already rose this issue to the support team and I had many exchange with them. I don't know if tey did something, but vertion 9.1.1 seem improved the behavior of C1 on this topic, but not solved it.
Nevertheless, I saw in you post you run C1 under Win10 as I do, and I want to share with you one possible way of improvement.
On My side, I migrated from Win7 to Win10 with microsoft update, but I wondered if a part of the issue took place one the migration of old setup.
So I completly rebuilt the system from scratch, and reinstall C1without keeping the previous configuration files.This drasticaly improve C1 behavior, but, unfortunatly it did not completly solved the memory leak issue.
Currently I always waiting for a complete solution and untill that, I restart C1 every 2 hours, to be sure not having a problem. ☹️
regards0 -
The points you make are interesting.
Since I installed 9.1.1. I am experiencing the spinning wheel all the time - for every adjustment.
I'm really not sure what the problem might be.
D.0 -
9.0-9.1 was really sluggish. 9.1.1 is better.
But I have 4 cores 4.2 GHz processor, SSD system disk and 16 Gb of memory and can't say that work of Capture One 9 is comfortable.
Is it real for the programmers of CO to optimize the work of next CO 9.1.2?0 -
Hi there,
I think clearing up the history files that are down in one of the %AppData% Local\CaptureOne folder in Windows might help. I had to do that a couple times in CO 8.x and haven't tried that since upgrading to 9.x.
The files are typically here:
C:\Users\<your user name>\AppData\Local\CaptureOne\Batch70
In the "history folder" you'll find files dating as far back as your first installation / use of Capture One.
If you close Capture One, move those files to another folder (e.g. Desktop\HistoryBackup), and restart Capture One, you might get that fresh-install feeling.
Another possibility is to just move the files that date back farther than recent history. These are basically recorded actions I guess from all your sessions.
That will probably break the chain of history for Capture One (it's in History.List - it's how Capture One knows what you've done before that's been serialized to your computer, and probably gets re-read every time Capture One opens). So it's probably better just to move the whole thing.
Anyhow, that's what I used to do. I'll probably try it out soon.
TTFN0 -
I've had 9.1.1 open all day hasn't moved past 5.7GB RAM usage - been adjusting images, adding adjustment layers, exporting JPEG files etc.. 0 -
[quote="gregger" wrote:
Hi there,
I think clearing up the history files that are down in one of the %AppData% Local\CaptureOne folder in Windows might help. I had to do that a couple times in CO 8.x and haven't tried that since upgrading to 9.x.
If you close Capture One, move those files to another folder (e.g. Desktop\HistoryBackup), and restart Capture One, you might get that fresh-install feeling.
...
TTFN
gregger, unfortunatly in my case , doing that did not solve the problem[quote="Bobtographer" wrote:
I've had 9.1.1 open all day hasn't moved past 5.7GB RAM usage - been adjusting images, adding adjustment layers, exporting JPEG files etc..
Bobtographer, could you tel us more about your system configuration(processor, OS version, use of openCL...)and you use of C1(camera,catalog or session, file format, continus use or only open, ...), this could help us(and the the support) to understand why we are so many to have memory leak issue.
regards0 -
[quote="JMR" wrote:
[quote="Bobtographer" wrote:
I've had 9.1.1 open all day hasn't moved past 5.7GB RAM usage - been adjusting images, adding adjustment layers, exporting JPEG files etc..
Bobtographer, could you tel us more about your system configuration(processor, OS version, use of openCL...)and you use of C1(camera,catalog or session, file format, continus use or only open, ...), this could help us(and the the support) to understand why we are so many to have memory leak issue.
Running an i5 with 32GB RAM, Win7 Pro x64 with a R9 390. Main RAW files come from a 7D2 (CR2). I use a single session and just point at a directory to work on. I work on files, then leave C1 open while doing other things ie. retouching files in Photoshop. (I run C1 for days without closing it)0 -
I find that adding styles slows to a crawl after I have been working C1 for about an hour, I just close and reopen that seems to do the trick 0 -
[quote="Bobtographer" wrote:
[quote="JMR" wrote:
Running an i5 with 32GB RAM, Win7 Pro x64 with a R9 390. Main RAW files come from a 7D2 (CR2). I use a single session and just point at a directory to work on. I work on files, then leave C1 open while doing other things ie. retouching files in Photoshop. (I run C1 for days without closing it)
Bobtographer: compare to my computer configuration, and I suppose also most of other user configuration, I notice one main difference. You have a powerfull graphic card how can manage traitment with OpenCL with a huge amount of memory in you video card and not with the system memory. I suppose it is the reason why you do not notice any problem with system memory.
regards0 -
[quote="JMR" wrote:
You have a powerfull graphic card how can manage traitment with OpenCL with a huge amount of memory in you video card and not with the system memory. I suppose it is the reason why you do not notice any problem with system memory.
regards
Memory usage on the Video card doesn't peak past 2300MB even when using local adustments..0
Post is closed for comments.
Comments
10 comments