Huge memory leak
Hi,
After installing C1 10, I opened a catalog folder, opened an image and played a little with it. Then I had something else to do and I left C1 running for about an hour. When I returned to my PC, the C1 process was occupying 1,5 GB and Windows (10) sent me a warning about that. A few seconds later, my system crashed.
After installing C1 10, I opened a catalog folder, opened an image and played a little with it. Then I had something else to do and I left C1 running for about an hour. When I returned to my PC, the C1 process was occupying 1,5 GB and Windows (10) sent me a warning about that. A few seconds later, my system crashed.
0
-
Any log file that I could retrieve somewhere ? 0 -
Please contact our Support. They'll take a look.
I am not sure why your Windows will warn about 1.5 GB of ram usage. That is fairly common for a modern complex application like Capture One.0 -
I have found the log files and among them the crash report. It contains numerous lines mentioning a leak detection.
I'll send them to the support.0 -
I submitted a case report as version 9, because as OP mentioned, there isn't an option to select 10, which debuted today. On my 16 GB system, I saw the usage went as high as 50% and it quickly went down. I left my C1PRO10 with 7942 mixed batch of RAWS (DNGs and CR2s) and 16-Bit TIFFs.
I submitted a case and attached relevant log files to the team to investigate the possible peculiarity.
OP: A software like C1PRO using 1-2 GB of RAM is considered "normal." I think your initial report of a possible memory leak might be onto something for the team to investigate. Today is its debut date. It's kind of expected for all on-arrival software releases.
The spike hitting 50% is only momentarily, it goes back down and goes up like a periodic motion.
Ron0 -
This has been a problem for me since I started using a catalog with Capture One 8. I think it's to do with Canon cr2 files. I've raised many support tickets, submitted logs, videos, screenshots, but it hasn't been fixed, and Phase 1 have never really acknowledged the problem. Right now my C1 process is using 31.56GB (my machine has only 16GB, so you do the maths). The only difference between 9 and 10 is that 10 doesn't seem to use Compressed memory. I've found that removing the Filters panel helps, or switching to a tab that doesn't contain the filters, but this is only after initially leaving it for a day or so. Force quitting C1 guarantees catalog corruption.
So if you're shooting Canon, I would strongly suggest that you stick to sessions.0 -
Hi Narq,
My catalog only contains RAF files produced by a X-Pro1.0 -
I don't think it's a memory leak, just that CO uses all the memory it can lay its hands on. Further it was no different in CO 9.
I've just spent a day working on my catalogue of 31000 images a mixture of Nikon NEF from D1H, D40, D2Hs and D700, Fuji X-Pro RAF and Sony ARW and have some interesting results.
First my machine has i7-3820 running at 3.6Ghz, 32GB RAM, GTX960 video card and catalogue is on Samsung SSD 850 EVO 1TB disk.
I started CO 10 this morning and it took 6min 23 sec to start and load all 31000 standard (1920 px) pre-views (at least that's what I think it was doing) at the end of which time it was using 3.51GB of memory. I then imported 12 pictures (Sony RX100 iii ARW) deleted 8 and worked on the other 3, memory usage rose to 5.74GB. I then worked on searching the database selecting pictures working on them etc and memory utilisation rose to 8.85GB.
On shutting down it took about a minute for memory to be fully released to the system.
The most annoying part of this is the start up time 🤓0 -
Hi David,
Your results are consistant with mine, except my Catalogue is around 102,000 images, stored on SSD. Start up time with catalogues is appaling - over 10 minutes before the interface appears, then a beachball for another 20 before you can use the interface. When I opened C1 my battery life was on 99%. It's now on 56%, and I've not been able to use any feature.
I'm amazed Capture One 10 was released with such a showstopping problem. As it is right now, Catalogues are pretty much unusable.0 -
[quote="Narq" wrote:
Hi David,
Your results are consistant with mine, except my Catalogue is around 102,000 images, stored on SSD. Start up time with catalogues is appaling - over 10 minutes before the interface appears, then a beachball for another 20 before you can use the interface. When I opened C1 my battery life was on 99%. It's now on 56%, and I've not been able to use any feature.
I'm amazed Capture One 10 was released with such a showstopping problem. As it is right now, Catalogues are pretty much unusable.
I would guess that this is not at all what the development and testing team are expecting.
Are you in communication with them about it?
If not you certainly should be.
Grant0 -
[quote="Samoreen" wrote:
Hi,
After installing C1 10, I opened a catalog folder, opened an image and played a little with it. Then I had something else to do and I left C1 running for about an hour. When I returned to my PC, the C1 process was occupying 1,5 GB and Windows (10) sent me a warning about that. A few seconds later, my system crashed.
I have the same bad experience, plus more, with my iMac computer and Capture One Pro 10. Tech support has not given me a suitable remedy. I may have to move over to a competitor.0 -
My catalog for 2016 has ~45,000 images in it. C1 10 is ready to work in ~6 seconds and is using about 950MB of ram. As I go through and view the contents of more and more folders in my catalog the ram usage goes up but it tops out around 3600MB.
I'm running Windows 10, 32GB of ram, my catalog is on an SSD, my archive of raws is on a mirrored array of two 7200 rpm hard drives. The system has a radeon r7 370 video card.
I left C1 running all day yesterday while I was at work and at the end of the day it was using 3100MB of ram.
Do you folks have your raws inside the C1 catalog or stored in a different location?
Have you used the "verify catalog or session" tool on your catalog?
I had a similar problem of very long load times and general unresponsiveness when I chose the "Full Sync" option in the "Auto Sync sidecar XMP" drop down in the Image tab of the preferences. Setting that to the default of "None" fixed that issue though.
This all sounds very frustrating, I hope you all are able to get this resolved!0
Post ist für Kommentare geschlossen.
Kommentare
12 Kommentare