CaptureONE PRO 5.1.2 "Out of Memory" Crashes
Can people chime in and share if they are receiving frequent "Out of Memory" crashes?
I am on a 64-Bit Win 7 8GB DDR3 RAM on Core i5. During the tagging/editing phase, I tend to get a lot of these crashes.
I am doing color tagging, deleted images I don't want, creating variants and applying the same processing settings to a set or the entire image session.
I am on a 64-Bit Win 7 8GB DDR3 RAM on Core i5. During the tagging/editing phase, I tend to get a lot of these crashes.
I am doing color tagging, deleted images I don't want, creating variants and applying the same processing settings to a set or the entire image session.
0
-
I get a LOT of these, and have had over 2 different PCS with xp and w7 and all recent versions of c1 pro (including 5.1.2). I now have a similar spec machine to you with w7 64.
I did raise a support case several months ago and went through several iterations of creating new sessions, reducing the number of files etc, but never got to the bottom of the problem.
My workflow is to do all the adjustments / tagging / deleting first and then process all the files I want in one hit, and I don’t usually continue using c1 while I am processing the batch. The crashes always happen while I am adjusting, although not consistently on any one tool.
I usually have several hundred (sometimes over 1000) files in the folder when I start (canon 5d mostly, some 20D and occasional 10D), and sometimes do an initial global copy or auto exposure across all of them with no problems.
The one thing I have noticed that I do is use the mouse scroll wheel a LOT to zoom, scroll thumbnails and adjust settings (hover the cursor over a numeric value and use the wheel – less clicking and hand movement required!) and often get crashes when I am doing that.
I’ve not had 5.1.2 installed for long enough to say whether it is better that other versions, but I’ve definitely had it crash like this.0 -
Yes, I get them quite frequently. I can't really correlate them to any given activity, though it does seem the more adjustments I have made to an image the more likely I am to see the crash. I mostly now start up C1 to edit one photo, possibly restart it a few times to edit that photo, and make sure to quite and restart when I want to edit another.
I'm on a Mac Pro 8-core Harpertown, Win 7 64-bit, with 24GB.0 -
You are not alone! 😭
Working on a AMD Phenom II X4 945 C3 with 8GB DDR2 RAM (memory-mapped) on Windows 7 Home Premium 32Bit0 -
[quote="net-explorer" wrote:
You are not alone! 😭
Working on a AMD Phenom II X4 945 C3 with 8GB DDR2 RAM (memory-mapped) on Windows 7 Home Premium 32Bit
Interesting configuration, 8 GB RAM with a 32-bit OS. Can you elaborate on the 'memory-mapped' configuration? Is it - for example - easy to switch it on/off? And have you ever considered a 64-bit Windows version?0 -
Also please reference viewtopic.php?f=20&t=8931 0 -
[quote="Paul_E" wrote:
[quote="net-explorer" wrote:
You are not alone! 😭
Working on a AMD Phenom II X4 945 C3 with 8GB DDR2 RAM (memory-mapped) on Windows 7 Home Premium 32Bit
Interesting configuration, 8 GB RAM with a 32-bit OS. Can you elaborate on the 'memory-mapped' configuration? Is it - for example - easy to switch it on/off? And have you ever considered a 64-bit Windows version?
Hello Paul_E,
I'm working with the memory-mapping since march 2010, and it's working absolutely stable and proper!
I red about it here, and thought on my older hardware, which is top and still working with 32bit-drivers!
The old DOS had a similar technology to use more than standard-RAM. This was the reason for me not to think on problems.
It's not necessary to switch, but you have the option between standard-Win7-Kernel and the off-limit-Win7-kernel by OS-loader.
Take this highly innovated kernel and some more RAM, and get lucky with it. That's really not a fake! Nastarovje! 😄
Unfortunately it couldn't help in the "out of memory"-problem. This must be a mistake in C1-Code independently on the CPU-architecture.0
Post is closed for comments.
Comments
6 comments