Some application licenses are geared to the hardware, so whenever I upgrade my hardware, I need to pay again to get another license. Money aside, a few 32bit application might not run smoothly in 64bit environment. Now PO is telling me that I have to continuously spend $$$ to buy a new PC, a Window 7 64bit license just to run C1 version 6. I spent another $150 to get a decent video card that supports OpenCL. I personally would not upgrade to 64bit Windows. Then version 6 will become a total failure. Given their quality history of version 6, even PO are afraid that such a change will introduce more errors and make even the 64bit version nonoperational. They are just reluctant to fix it as fixing it would mean a large portion of code/logic need rewritten. In fact they know what codes had been added in version 6 and which of them will cause memory trouble. Only a few functions will allocate memory from the OS.
Computational logic would not consume much memory. I don't think PO don't know where the problem is. As I explained above, the problem was caused by inefficient/uncontrollable memory usage by C1 and limit of 32bit windows. Upgrade to 64bit Windows will definitely minimize the chance of this notorious OOM error.
If PO staff think that their design and coding are perfectly right, then C1 v6 does not fit to run under x86 Windows and they should state so (only 圆4 supported) in the minimal system requirement and let we customer know before we pay our money to purchase/upgrade.Ģ) this week, after having studied my log files, to upgrade my entire system as the 64 bit version is supposedly better suited Why C1 6 need so much virtual memory? Obviously a programming bug or inefficient codes such that memory is only allocated but never returned to the OS. So any suggestion to add more RAM or increase the paging file size will not solve the problem.
So even though you have 4GB physical RAM installed, if C1 attempt to claim more than 2GB for its virtual memory, you still get "Out of memory" error. LR3.3 need only 700MB Virtual Memory to begin with.Īll x86 (32bit) Windows, no matter WinXP Pro, Vista or 7, allow only 2GB virtual memory max for any single process. When I start C1 6.01 for a folder with less than 10 photos, the virtual size is over 1GB already. You can imagine Virtual Memory as some working space claimed by a program. You need to use Process Explorer from sysinternals (now Microsoft) to see the difference. Task manager shows the so-called Working Set size, memory spaces that are physically loaded into RAM to run. What matters here is the virtual memory size used by C1.