memory leaking bad!
Not new topic. I saw the thread about 9.0.1 leak. Supposedly there was a patch too. But this one is 9.0.3. Memory leaks must have been fixed already.
Still leaking, badly too... How to reproduce. Very easy. Load 1000 canon raw files. and go from the first one up, just reviewing, assigning stars. At the start the memory usage is about 3.5Gb, but when you reach the middle of the list, memory usage will be 15Gb.
At which point you will notice delays, visual delays, redrawing the picture when you zoom in and zoom out. Also, if you try to delete a file (Del key - move to trash), it will take 5-6 seconds for each file, and quite likely, you will see also, the preview generation process starting for no good reason (right after a file has been deleted), generating all the previews again.
Also, when at this point (in low memory), the database will get corrupted EVERY time (happened 3 times to me today)
Maybe this database corruption is related to how the low memory condition is handled in C1.
I am thinking about making the first pictures review and in PS bridge now as before, cut down to 30% there and then correct and convert using C1... Until C1 works with large sets. As it is now, it is basically not functional.
Still leaking, badly too... How to reproduce. Very easy. Load 1000 canon raw files. and go from the first one up, just reviewing, assigning stars. At the start the memory usage is about 3.5Gb, but when you reach the middle of the list, memory usage will be 15Gb.
At which point you will notice delays, visual delays, redrawing the picture when you zoom in and zoom out. Also, if you try to delete a file (Del key - move to trash), it will take 5-6 seconds for each file, and quite likely, you will see also, the preview generation process starting for no good reason (right after a file has been deleted), generating all the previews again.
Also, when at this point (in low memory), the database will get corrupted EVERY time (happened 3 times to me today)
Maybe this database corruption is related to how the low memory condition is handled in C1.
I am thinking about making the first pictures review and in PS bridge now as before, cut down to 30% there and then correct and convert using C1... Until C1 works with large sets. As it is now, it is basically not functional.
0
-
It's not just Catalogues though, it does the same with Sessions. Your 1st Session uses approx 3-4gb of memory and then increases by a similar amount for each Session you open. If you close a session, or all of them bar one, the memory used by C1 does not return to the original 3-4gb, it stays at the amount allocated when you had multiple Sessions open.
At one point I was able to get it to 25gb after opening several sessions and closing them all to leave one left. It slowed and crashed of course and software designed to reclaim memory could not get it back from C1. If you close C1 and reopen it with the one Session you need to work on, then it will return to 3-4gb again.0
Post is closed for comments.
Comments
61 comments