Skip to main content

'Out of Memory' Crash - anyone else?

Comments

90 comments

  • Florin Coter
    Yes, of course. Many of us. Just read the forum. As to PO not being able to recreate, I think they simply have no idea of debugging and testing.
    0
  • Urukhai
    I was shocked to learn that PO is denying this "Out of Memory" for WinXP 32bit. 🤬
    Beside being ignorant in quality and testing, they are arrogant and have no sense of responsibility.
    Even a non-professional user knows how to trace the CPU & memory usage. What PO programmers are doing?
    0
  • NB
    fyi - I reported to PO that I have 4989MB of virtual memory allocated, initial and max. They are recommending I increase it to see if this eliminates the crash.
    0
  • Urukhai
    The max RAM 32bit Windows can access is 4GB. What a sensible and professional recommendation from PO support!
    A typical RAW file size for a DSLR is just 20-30MB. 4GB is already a lot (100x) . LR3.3 uses a footprint of 500-700 MB to run.
    If PO is giving up support to x86 Windows community, pls state them in the minimal system requirement.
    I hate hardware upgrade to cover up inefficient programming. Shall I get the same computer used by NASA to run CO, ridiculous !
    0
  • Piet Gispen
    I too run into these difficulties and am getting the same advice, all to no avail. While version 5.xx wasn't too stable, it was heaven compared to 6.xx (paid upgrades). I have tried really everything, but nothing seems to help. All other software just seems to run fine on the same XP 32-bit system. I am getting pretty desperate as it taking too much of my time and costing me a lot of money.
    Piet Gispen Photography
    0
  • NB
    yes this is taking a lot of my time testing each new release, gong back and forth with support trying different things. but 6.1.1 still crashes so much it is unusable. 5.x and previous never crashed.
    0
  • Pjotr
    I'am test driving CO6.1 now for about 3 weeks and no crashes or memory leaks at al. Although my RAW files are rarely over 12 MB in size. System: Pretty standard Win XP Pro on a 2.4 gig Athlon dual core machine with 4 GB Ram.

    I don't want to ignore the mentioned problems here, these are serious enough. But some more help and insight from the users, instead of bashing, can help PO to solve this if they can't reproduce it.

    I'am using Cacheman for watching memory usage and solving some memory problems. Hé, CO6 is not the only program with memory leaks 😁 What I noted: CO6.1 starts up with about 550 MB memory claim and rarely goes over 750 MB when doing 12 MB RAW files or browsing folders within CO.

    Maybe these problems appear with much larger files?
    0
  • NB
    My RAW files are smaller I believe (canon 30D). I notice that with a 200 image directory it starts up at about 350mb memory (as shown in memory usage in task manager). After I scan thru a few files, a few simple edits it settles at about 800mb. But then (and I need to do more experiments) it starts peaking over 1000mb here and there, i can lower it my switching to a different image, or sometimes I do another edit operation (saturation, rotation, noise reduction) and I get the crash. There a big boosts in usage when I open a new directory.
    0
  • Urukhai
    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
  • NB
    This is the last entries in imgcore.log:

    bmpRef = 227773416
    procRef = 5
    2011-02-16 17:27:50.703> (ERROR) Could not allocate Block of [44368128] bytes
    2011-02-16 17:27:50.906> (ERROR) Could not allocate Block of [44368128] bytes
    2011-02-16 18:58:49.687> (ERROR) Exception in CTileExecuter::lowLevelExecute, current operation=[Resampling], step=10
    2011-02-16 18:58:50.640> (ERROR) Exception in CTileExecuter::lowLevelExecute, current operation=[NoiseSuppression], step=5
    2011-02-16 18:58:55.718> (ERROR) Operation did not finish; worker thread killed.
    0
  • Jean1
    I run Windows XP Family (SP3) on an Intel Core 2 Duo CPU E8400 @ 3.00Ghz.with 4Go de RAM. My graphic card is among those supported for Open Gl (Nvidia GF 8800GT Zalman with 512Mo). I use 2 monitors.

    Before I open CO Pro v.6.1.1 the memory used is about 500Mb. As I open CO, memory used jumps to 1.6Gb (this is just for opening, at this stage I haven't done any ajustment or processing yet).

    As I work on my photos (about 15000Kb NEF files) the memory used can go up to 2.4Gb and I often crash. One sure way to trigger a crash is to work on local adjustment, which pumps up a lot of memory.

    I was much happier with CO5. My opinion is that CO6 was launched prematurely just before Christmas so as to generate sales, even though the product was not stable. It still is not. I wish I had tested it more thoroughly before I paid for the upgrade...
    0
  • Paul725
    On Win 7 professional 64bit, 8gb of ram, I kept opening folders containing RAW files, CaptureOne.exe was taking more and more memory, I stopped when it got to 1,469,352 kb

    It just continues to grow, not a problem for me with the 64 bit version , but if the 32 bit appliction behaves in the same way I am not supprised you get problems
    0
  • HKGuns
    I've not noticed the cause of mine on Vista32, however, the 6.1.1 is crashing WAY too often for my tastes. PO needs to get this version stabilized more quickly than they are currently progressing.
    0
  • s ss
    i'm happy! at last i have the same message. so everything OK, i'm in "team". 😁
    0
  • NB
    I've noticed the crash is much more frequent (i.e. rapidly assured) if one load up a directory of images that have a lot of rotation and cropping. I can get thru about 5 such images in a directory before it crashes.

    When in full screen mode the 'out of memory' dialog box appears behind CO window. CO usually remains semi functional after the crash - for example the sliders can still be moved, but they do nothing. Or one can change between images using arrow keys, but the exposure graphs, etc. stay empty (like when selecting a video file)

    6.x remains useless to me until this is fixed.
    0
  • Urukhai
    What a surprise 🙄 Drew, Paul_E or Lionel did not say a word on this thread.

    Can some one from PO tell us when this notorious Out of Memory error will be fixed !
    0
  • Paul Steunebrink
    [quote="Urukhai" wrote:
    What a surprise 🙄 Drew, Paul_E or Lionel did not say a word on this thread.

    Can some one from PO tell us when this notorious Out of Memory error will be fixed !

    Hi Urukhai, can you tell me why you expected me to reply? The OP (Alex1) asked others users with the same problem to respond. I am a user, not affiliated with Phase One in any way, and do not encounter this problem.

    However, that someone is missing my contribution will be taken it as a compliment. 😉
    0
  • Jean1
    Well, has any one of us created a support case ? I haven't as I thought the issue was known and that the PO staff were working on it. I intend to create one promptly.
    0
  • Jean1
    I have just created a support case.
    0
  • NB
    Thanks jean1.
    That was my primary intent of this thread, to remind users who have this problem to open a support case. It is the only way this will get fixed. The other intent was to share what versions/systems/conditions cause the OOM crash so it can help focus the reports we give to PO.
    0
  • Jean1
    PO reacted very quickly to my support case request (they asked for a few .log and .nfo files). Let's hope they can make sense out of it.

    My experience with them is that they have always been reactive. I am writing this as I feel that they have often been criticized unfairly.

    I would like to encourage all the forum members who contributed to this thread to open a support case too, this will help to solve this frustrating issue.
    0
  • Piet Gispen
    [quote="Jean1" wrote:
    I have just created a support case.


    I have started a support case as far back as december of last year. So far, no one has been able to really help. I have been given the advice 1) to downgrade back to version 6.0, because that is supposed to be more stable (in my case however this is where my problems started..., so I did not downgrade) and 2) this week, after having studied my log files, to upgrade my entire system as the 64 bit version is supposedly better suited, but mostly since the support team does not have a clue what is actually causing all the mishaps. I haven't done so either, as my system (32 bit XP SP 3, 4 gig RAM, compatible video card etc) is doing fine with all other software.

    Piet Gispen
    http://www.pietgispen.com
    0
  • Jean1
    [quote="Piet12" wrote:
    my system (32 bit XP SP 3, 4 gig RAM, compatible video card etc) is doing fine with all other software
    Piet12, we have the same configuration and the same problems with CO6. All my other software works smoothly too.
    0
  • NB
    Same config here (winxp sp3, 4gb mem, compatible mem card)

    Also have had a support case to address these frequent crashes since Dec. 6th

    All my other SW works perfectly and I have never once had a crash with the final releases of v3, v4 & v5
    0
  • Urukhai
    [quote="Piet12" wrote:
    [quote="Jean1" wrote:
    I have just created a support case.


    2) this week, after having studied my log files, to upgrade my entire system as the 64 bit version is supposedly better suited

    Upgrade to 64bit Windows will definitely minimize the chance of this notorious OOM error. As I explained above, the problem was caused by inefficient/uncontrollable memory usage by C1 and limit of 32bit windows.

    I don't think PO don't know where the problem is. Computational logic would not consume much memory. Only a few functions will allocate memory from the OS. In fact they know what codes had been added in version 6 and which of them will cause memory trouble. They are just reluctant to fix it as fixing it would mean a large portion of code/logic need rewritten. 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. Then version 6 will become a total failure.

    I personally would not upgrade to 64bit Windows. I paid the upgrade fee to version 6. I spent another $150 to get a decent video card that supports OpenCL. 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.

    Money aside, a few 32bit application might not run smoothly in 64bit environment. Some application licenses are geared to the hardware, so whenever I upgrade my hardware, I need to pay again to get another license.

    So upgrading to 64bit is just an easy solution for PO to make up their incompetent. We customer have to bear all the financial consequences and upgrade hazard. Where is the justice?
    0
  • LadyRainbows
    I upgraded to Win 7 64 and 4GB DDR3 1066 recently, I no longer get this error. 😄 I don't regret it either as C1 runs 600X faster!
    0
  • NNN634236227273766629
    Hey folks. I have not had repeated crash episodes with C1, BUT my other program, Nikon's Capture NX2 has had huge problems. A Sony Vaio program saw the crashes and put my Vaio on to some patches... one in paticular was an Intel (yes that Intel) patch for fast transfer of data into RAM. So far so good. We will see how it goes.
    My point is the problems could be deeper than C1 and, happily, fixable.
    0
  • NB
    Still no fix. So I am still using 5.x, but really wanting to use 6.x for dust spots and other improvements.

    Latest (March 7th) update from Phase One:
    "No update just yet, we are still working on identifying the issue. Thank you for your patience."
    0
  • Jean1
    [quote="Alex1" wrote:
    Still no fix. So I am still using 5.x, but really wanting to use 6.x for dust spots and other improvements.

    Latest (March 7th) update from Phase One:
    "No update just yet, we are still working on identifying the issue. Thank you for your patience."

    I got tired of waiting and I have finally upgraded to Windows 7 Pro 64-bit with 8GB of memory because I was so frustrated with the behaviour of Capture One 6 with XP 32-bit ("out of memory").

    It works smoothly and fast but now I have no connection with Expression Media from within C1. This is a minor inconvenience which I hope can be fixed.
    0
  • Paul Steunebrink
    [quote="Jean1" wrote:
    ...
    It works smoothly and fast but now I have no connection with Expression Media from within C1. This is a minor inconvenience which I hope can be fixed.

    See my workaround for Expression Media connectivity in a Win 64-bit environment.
    viewtopic.php?p=45523#p45523
    0

Please sign in to leave a comment.