'Out of Memory' Crash - anyone else?
There has been some discussion about this crash, first seen in 6.1 and still for some in 6.1.1:
viewtopic.php?f=41&t=10042
viewtopic.php?f=41&t=10110
I still get this crash in 6.1.1 32-bit Express on WinXP, 4GB memory. Fully clean install per PO instructions.
At this point I am being told PO can not recreate and to check my virtual memory settings (they are default). I never had this issue until 6.1 and never changed any system settings.
If I keep the task manager open I can watch the memory usage of CO. It starts at ~300,000k, then slowly keeps creeping up as I make minor edits. Each time I open a new directory of images it jumps ~200,000-500,000k depending on size. Then when it gets over ~1,000,000k the out of memory crash occurs.
I ask that if anyone else has this issue (I know some have noted they do) to please open a support case if you have not already and provide your capture one logs.
viewtopic.php?f=41&t=10042
viewtopic.php?f=41&t=10110
I still get this crash in 6.1.1 32-bit Express on WinXP, 4GB memory. Fully clean install per PO instructions.
At this point I am being told PO can not recreate and to check my virtual memory settings (they are default). I never had this issue until 6.1 and never changed any system settings.
If I keep the task manager open I can watch the memory usage of CO. It starts at ~300,000k, then slowly keeps creeping up as I make minor edits. Each time I open a new directory of images it jumps ~200,000-500,000k depending on size. Then when it gets over ~1,000,000k the out of memory crash occurs.
I ask that if anyone else has this issue (I know some have noted they do) to please open a support case if you have not already and provide your capture one logs.
0
-
One thing i've noticed on my XP 32 bit rig; when monitoring main and virtual memory usage with task manager; as i do basic edits on an image, memory usage steadily climbs to in excess of 1 gig of VM and around 0.9 gig of main memory. Then crashes or I get an out of memory mesage. If I minimize the app window and then restore, memory usage figure drops dramatically and them climbs again as i do basic exposure, curves etc edits. Why is so much memory released when doing a windows minimize restore? My video card is a Radeon 4670 with1 gig cache. Also using dual monitors. Camera is Canon 7D. I have reported my issues to CO support by the way. No such issues with v5. Alhough I realize v6 has much more functionality and features than v5 I do not have such issues with Adobe CS 5. 0 -
[quote="Mal3" wrote:
One thing i've noticed on my XP 32 bit rig; when monitoring main and virtual memory usage with task manager; as i do basic edits on an image, memory usage steadily climbs to in excess of 1 gig of VM and around 0.9 gig of main memory. Then crashes or I get an out of memory mesage. If I minimize the app window and then restore, memory usage figure drops dramatically and them climbs again as i do basic exposure, curves etc edits. Why is so much memory released when doing a windows minimize restore? My video card is a Radeon 4670 with1 gig cache. Also using dual monitors. Camera is Canon 7D. I have reported my issues to CO support by the way. No such issues with v5. Alhough I realize v6 has much more functionality and features than v5 I do not have such issues with Adobe CS 5.
I noticed the exact same memory usage climb and 'out of mem' crash point. I have not tried the minimize trick though.
I don't use dual monitors and don't have any other apps running at the same time.
Since I use Express and as I have noted a few times previously, even if I don't use any of the few new features in v6 (tested by simply browsing images, not even editing, that have only ever been edited in v5) it will still crash with the 'out of mem.' message. Thanks for reporting.0 -
I am now falling back on V6.01, which still has the redraw artifact but I rarely experience OOM error. In the later version 6.1 & 6.2, the artifact has gone but in return I get OOM.
I strongly suspect this Out of Memory error is a consequence of how PO team solved the flickering and redraw artifact (momentary screen corruption) when invoking GPU/OpenCL. Flickering happens when there is only one copy of Video RAM for both GPU to work and display. If there are 2 versions of VRAM, GPU can work on one copy and the other version can be used for display until GPU finish their work.
I believe in the later version PO has made copies of Video RAM to system RAM to solve the flickering issues. This might explain why the Memory usage grows so fast and why minimizing and restoring the C1 program window will reduce the memory usage.
This also explains why PO took so long to fix this OOM issue. Because when they stop making copies of Video RAM, the flickering and redraw artifact will come back again and many users (at least 64bit users) will consider them as bugs.
If that was really the way how PO team solved the flickering, I prefer to have it back at least for 32bit C1 such that I can have a stable software.0 -
I think (specifics can be found on this forum) one or more of the early versions of v6 had a certain crash (i recall maybe even OOM) when running a slideshow. Not that it is an essential capability. 0 -
I reported my out of memory and app crash to Support and also informed them of my pending upgrade to new computer and OS from XP 32 bit to Win 7-64 bit.
I was advised that one potential bottle neck, is not necessarily the graphics card ( i asked if my new one would be insufficient) but the hard drive speed. They recommeded 7200 rpm amd preferrably 10,000 rpm, SSD or Raid.
They also stated that v6.1.1. would be released next week and should solve some of these issues. That's encouraging news.0 -
Did they or you mean 6.2.1? 0 -
I should proof read ☹️
6.2.10 -
I am eagerly awaiting. Especially if they think it will address 'some of these issues' 0 -
[quote="Mal3" wrote:
They recommeded 7200 rpm amd preferrably 10,000 rpm, SSD or Raid.
I have been using SSD since V6.0. SSD definitely does not help the OOM ❗️0 -
I downloaded 6.2.1 this morning and hope to have time to test it this evening after work. 0 -
[quote="Alex1111" wrote:
I downloaded 6.2.1 this morning and hope to have time to test it this evening after work.
Release note highlighted only MAC 8 cores problem. Not a single word on 32bit Windows. I don't have high hope on this release ☹️0 -
Sadly you are right. 6.2.1 Express WinXP 32-bit.
In fact the crash happens much quicker and it is no longer an 'out of memory' crash, but a 'sorry capture one has unexpectedly quit' with an option to send an error report.
Watching memory usage (using task manager) it very quickly with each new image browsed went from ~500k to 600, 800k, then 900, 970 and finally 1,050 and crash. Boom.
So obviously some code related to this was changed, but with no fix, just made it even less usable than 6.2. Sigh,0 -
What additions or improvements has this update brought?
What errors or bugs has this update supposed to have addressed (if any)?
Is this information available anywhere?
Don't get me wrong, if this program worked as promised, it would be pretty good to say the least. Its just a shame all of these errors and problems are blotting its copy book.0 -
[quote="Alex1111" wrote:
In fact the crash happens much quicker and it is no longer an 'out of memory' crash, but a 'sorry capture one has unexpectedly quit' with an option to send an error report.
This was really a nasty way to solve the OOM error, by giving it another name 🙄0 -
Trying C1. Keeps freezing. Running Windows 7 4 gb touch screen all in one bought less than a year ago. Lightroom ran fast and efficiently. This is almost unusable, I sit and WAIT WAIT WAIT. What's up with this PRO program. I am shooting 24 MP raw files with Sony Alpha 850. [quote="Urukhai" wrote:
What matters here is the virtual memory size used by C1. Task manager shows the so-called Working Set size, memory spaces that are physically loaded into RAM to run. You need to use Process Explorer from sysinternals (now Microsoft) to see the difference. You can imagine Virtual Memory as some working space claimed by a program.
When I start C1 6.01 for a folder with less than 10 photos, the virtual size is over 1GB already. LR3.3 need only 700MB Virtual Memory to begin with.
All x86 (32bit) Windows, no matter WinXP Pro, Vista or 7, allow only 2GB virtual memory max for any single process. 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. So any suggestion to add more RAM or increase the paging file size will not solve the problem.
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.
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 x64 supported) in the minimal system requirement and let we customer know before we pay our money to purchase/upgrade.0 -
Having the same "out of memory" crashes with C1 version 6.2.1 on my system (XP SP3, 4 gb ram, Intel Duo Core 2.33Hz) and after reading Urukhai's posting and Alain's posting about "memory usage as cache?" (I've noticed the same memory grow using fullscreen F10), I've tried the virtual memory-setting mentioned in this article http://msdn.microsoft.com/en-us/windows ... e/gg487508 and since then I've got no "out of memory" crashes anomore.
Perhaps others could try the same setting and report back if there "out of memory" crashes are also gone.
René
The Netherlands0 -
[quote="NNN634424949283208518" wrote:
Trying C1. Keeps freezing. Running Windows 7 4 gb touch screen all in one bought less than a year ago. Lightroom ran fast and efficiently. This is almost unusable, I sit and WAIT WAIT WAIT. What's up with this PRO program.
Not to be a jerk about it, but if you are a pro looking for pro performance, what are you doing using a 4gb touch screen all-in-one as your processing box? The fact that it's only a year old is irrelevant: it is not, by definition, a serious imaging workstation.
I'm certainly not a pro, but I've still got my modest Win 7 64 bit machine maxed out (with "only" 8gb) and Cap One is rock solid.
I have some issues with Cap One, but stability and performance aren't among them.
You've got Win 7 (not 32 bit, I presume) so use it - the whole point of 64 bit operating systems is to make maximum use of available RAM, and every converter I've installed in the last year - Lightroom, Cap One, Bibble 5, and even Raw Therapee - has needed, and has benefited hugely from, as much RAM as I could give it.0 -
[quote="Ren�91" wrote:
Having the same "out of memory" crashes with C1 version 6.2.1 on my system (XP SP3, 4 gb ram, Intel Duo Core 2.33Hz) and after reading Urukhai's posting and Alain's posting about "memory usage as cache?" (I've noticed the same memory grow using fullscreen F10), I've tried the virtual memory-setting mentioned in this article http://msdn.microsoft.com/en-us/windows ... e/gg487508 and since then I've got no "out of memory" crashes anomore.
Perhaps others could try the same setting and report back if there "out of memory" crashes are also gone.
René
The Netherlands
In my opinion this workaround doesn't help in this case most of this users. I did the same since more than a year with Windows 7 32Bit Home Premium, 8GB RAM, and it runs perfectly stable with all my software all the time.
But C1 v6pro is the exception, the only, and the same case like the v5 pro from its first time to v5.2 on my XP-System and other hardware before!! The same "out of memory"-crashes!!!
But if you compare the details of this issue wrote in all the web, you will see there are many different PC-Systems with 32- and 64-Bit OS, and memory from 2GB up to 16GB, and also MAC-Systems too!
In my case I cant understand why C1 don't use the 32bit-max. of memory per application, therefore I spend 8GB of RAM. But however, should it use less than this, and use the HD-Cache, but don't crash after something about more ore less than five pics again and again.
With the version 5.2 pro I got a stable C1 pro on my 32 bit system, and it was working also stable till these days on my following PC system. First changed from Win XP to Win7, than changed the hardware too, also RAM from 4GB to 8GB and the memory-mapping-functionality. No more problems at all!
And then came this v6 pro...!!!0 -
[quote="net-explorer" wrote:
In my case I cant understand why C1 don't use the 32bit-max. of memory per application, therefore I spend 8GB of RAM.
Not much point putting 8gb onto a 32 bit operating system.
If you were to put Windows 7 64 bit onto your machine, I bet you'd be very happy. Yes, it's a drag having to upgrade an OS to make full use of your available memory, but all your software would thank you for it.0 -
[quote="Keith Reeder" wrote:
[quote="net-explorer" wrote:
In my case I cant understand why C1 don't use the 32bit-max. of memory per application, therefore I spend 8GB of RAM.
Not much point putting 8gb onto a 32 bit operating system.
If you were to put Windows 7 64 bit onto your machine, I bet you'd be very happy. Yes, it's a drag having to upgrade an OS to make full use of your available memory, but all your software would thank you for it.
I upgraded from XP Family 32-bit with 4GB to Win7 Pro 64-bit with 8GB. My applications don't run faster but C1 Pro 6 has at last become stable.0 -
You may include me too.
WinVista 32 bit SP2
AMD Athlon 64 X2 4200+ / 2 GB ram
Problem arrived since installing 6.2.1 a few days ago.
Did not experience this problem with C1 6.1 (have to download it again to try)
Used memory increases even when not touching the computer until > 1.2 Gb -> windows crash.
Just 2 canon raw files (G9) present in move in folder
file #1 Keystone vertical & Lens cast (light fall off) & Crop (because of LCC)
file #2 Lens cast (light fall off) & Crop (because off LCC)
Have the thumbnail viewer OFF (<Ctrl>+B)
select File #1: memory increase from 614mb to 935mb ('slow' increase consumption 20..50mb at a time )
select File #2: memory decrease from 935mb to 614mb (fast 'drop' of memory 3 steps of ~100mb)
Both actions are combined with 100% cpu load during increase/decrease.
Also happens when C1 is running minimised.
Can't reproduce it with thumbnail viewer ON
That's it for today, will try to investigate (if I have time)
Regards,
Kees0 -
Hi!
Have an laptop ascer aspire 5738ZG: Win 7, 32Bit, Dual Core 2.0Ghz, 3GB RAM
But since the 6.2.1 upgrade I often have crashes and two errors:
1. Out of memory
2. Restart application.
What is happening? The super software for professional photographers is not working stabil???
Does C1 customers get a free patch or update?
Regards
Arthur
Cologne, Germany0 -
All patches/updates within version 6 are free until sofar (if you have a license)
How much memory do you have available (see task manager <CTRL>+<SHIFT>+<ESC> and then tab 'performance'
What does not work for me, but might work for you (as you have 3GB ram) (I am limited to 2GB and cannot plugin extra ram)
[url]http://www.phaseone.com/en/search/article.aspx?articleid=2049&languageid=1
[/url]
read completely before doing!
I have downgraded to 6.1.1 as it uses 'only' 750MB of ram, resulting in a total ram usage of 1,5GB (and no crashes)
6.2.1 needs about 250..400 MB ram in addition0 -
Thank you Kees for referring to the knowledge base article about the 3GB switch.
@User NN252145UL with his Acer Aspire 5738ZG: you could consider upgrading to 4 GB RAM to extend the life of your machine
@Kees: surprised that an Athlon 64 X2 machine has a 2 GB RAM limit0 -
@ Paul:
it is a Asus barebone (Pundit P1-AH2), did not want a large noisy box.
Never had troubles until I installed 6.2.10 -
This error has been hanging for more than 6 months. And still P1 has no plan to fix it 🤬
This thread had been quiet for quite some time because many of us have given up hope on P1.
I am just waiting for LR to pick up quality and speed and then the era of C1 will be over.0 -
[quote="Kees" wrote:
@ Paul:
it is a Asus barebone (Pundit P1-AH2), did not want a large noisy box.
Never had troubles until I installed 6.2.1
Clear. However, more features more space required.0 -
[quote="Urukhai" wrote:
...
This thread had been quiet for quite some time because many of us have given up hope on P1.
I am just waiting for LR to pick up quality and speed and then the era of C1 will be over.
I think users who encountered this error either moved to 64-bits Windows (and asked themselves what took them so long) or some might have reverted to CO5. For Capture One, the 32-bits era slowly comes to an end.
Users asked (screamed) for 64-bits software; hence we got it. Phase One added features; we love it. It did not work out well for a minority of 32-bit hardware configurations; we all regret it. Phase One did some tweaks but there is no way back; let's face it.0 -
Remember that windows 32 bit can only address 4gb and this includes the video card memory
If you have a 1gb video card, it’s pointless having any more than 3gb of RAM in the machine, any more cannot be used.
The numbers are approximate.
I believe that win 7 64 bit nome premium is limited to 16gb of ram, this is Microsoft’s decision not a physical limitation,0 -
[quote="Paul_E" wrote:
Users asked (screamed) for 64-bits software; hence we got it. Phase One added features; we love it. It did not work out well for a minority of 32-bit hardware configurations; we all regret it. Phase One did some tweaks but there is no way back; let's face it.
I had stated the same story long time ago. I don't mind P1 giving up the 32bit user community for whatever reasons.
It is their business decision. But if that is the case, then admit it in the system requirement that V6.2 does not run on Win32 platform and give warning to customers of the potential risk of constant fallover. Or even stop selling 32bit and offer refund to those customers who now regret upgrading to version 6 as v6 Win32 is not functioning to expectation if P1 is an honest and socially responsible company.0
Post is closed for comments.
Comments
90 comments