10.5+ GBs RAM ImgCoreProcess.exe DURING Web Contact Sheet?
My dearest fellow C1PRO users,
I am curious if you also experienced a big delay/lag between pressing the "Export" within the Web Contact Sheet and the software's actual Web Contact Sheet creation?
On my system, i5 750 @ 2.67 GHz @ 16 GB DDR3 RAM, the ImgCoreProcess.exe goes up to 10.xx GB!!! [This is during the creation of the Web Contact Sheet].
I submitted a Support Case to see if this was "normal."
I am thinking...10.5x GBs for the Web Contact Sheet is "bloaty" don't you think? Once the Web Contact Sheet has been successfully exported, the ImgCoreProcess.exe **remain** at 10.5x GBs! Is that normal? I am looking at the "Process" tab on my Windows 7 Home Premium SP1. This is when I am viewing the Windows Task Manager.
I am curious if you also experienced a big delay/lag between pressing the "Export" within the Web Contact Sheet and the software's actual Web Contact Sheet creation?
On my system, i5 750 @ 2.67 GHz @ 16 GB DDR3 RAM, the ImgCoreProcess.exe goes up to 10.xx GB!!! [This is during the creation of the Web Contact Sheet].
I submitted a Support Case to see if this was "normal."
I am thinking...10.5x GBs for the Web Contact Sheet is "bloaty" don't you think? Once the Web Contact Sheet has been successfully exported, the ImgCoreProcess.exe **remain** at 10.5x GBs! Is that normal? I am looking at the "Process" tab on my Windows 7 Home Premium SP1. This is when I am viewing the Windows Task Manager.
0
-
Hey, I am getting quite the same while and after building previews - mem consumption rises up to 5-6 Gb of my 8Gb. And it doesn't release when it's done. Only restarting C1 helps.
I suppose there's very noticeable memory leakage issue in that version (C1 pro 6.3.3 @ Win7x64)0 -
Submit a Support case and please reference this thread and the case #100469 I placed with Tech Support. [quote="NN108190UL2" wrote:
Hey, I am getting quite the same while and after building previews - mem consumption rises up to 5-6 Gb of my 8Gb. And it doesn't release when it's done. Only restarting C1 helps.
I suppose there's very noticeable memory leakage issue in that version (C1 pro 6.3.3 @ Win7x64)0
Post ist für Kommentare geschlossen.
Kommentare
2 Kommentare