Zum Hauptinhalt gehen

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Upgrade to 4gb - CO4.6 crashes

Sean321
We upgraded our ram to 4gb on our MBP 2.3 and 2.4ghz 17" notebooks (running 10.5.6 and CO4.6) because they became too slow to work effectively.

But now we crash CO on both machines seconds after opening up...

========

Process: Capture One [173]
Path: /Applications/Capture One.app/Contents/MacOS/Capture One
Identifier: com.phaseone.captureone
Version: Capture One 4.6 (4.6.24882)
Code Type: X86 (Native)
Parent Process: launchd [73]

Date/Time: 2009-01-13 12:26:24.143 +0200
OS Version: Mac OS X 10.5.6 (9G55)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000001
Crashed Thread: 0

Thread 0 Crashed:
0 libSystem.B.dylib 0x90efde42 __kill + 10
1 libSystem.B.dylib 0x90f7023a raise + 26
2 libSystem.B.dylib 0x90f7c622 __abort + 97
3 libSystem.B.dylib 0x90f7c68a _cproc_fork_child + 0
4 com.phaseone.captureone 0x001956c7 0x1000 + 1656519
5 libSystem.B.dylib 0x90efc2bb _sigtramp + 43
6 ??? 0xffffffff 0 + 4294967295
7 com.apple.AppKit 0x969ae96c _NSDefaultTopLevelErrorHandler + 135
8 com.apple.AppKit 0x967a4564 -[NSApplication run] + 532
9 com.apple.AppKit 0x967718a4 NSApplicationMain + 574
10 com.phaseone.captureone 0x000028cb 0x1000 + 6347
11 com.phaseone.captureone 0x000027f9 0x1000 + 6137

==========

and about 30 other threads
0

Kommentare

15 Kommentare

Datum Stimmen
  • Gareth
    I'm sorry I can't be of any real help but I don't understand this 2GB memory limit.

    I run 12GB of RAM in my Mac Pro and since 4.5.2 and now 4.6 I've not had a crash yet.
    0
  • Sean321
    Is there any way I can assign only 2gb to CO4.6 from the system side? everything else works fine... so I know it's not bad memmory modules
    0
  • Sean321
    seriously confused... one machine started working... the other still crashes... both machines set-up exactly the same...
    0
  • Sean321
    Cancel that... The machine that was running crashed after processing 304 of about 640 images... and now crashes everytime I start the queue...
    0
  • Paul Steunebrink
    [quote="Sean" wrote:
    Is there any way I can assign only 2gb to CO4.6 from the system side? everything else works fine... so I know it's not bad memmory modules

    Unfortunately that conclusion appears to be false more often than not. Even if only one application crashes (after a memory update) and many others are running fine, it can still be a bad memory module.

    Note that in some older MBPs (typically before 'Santa Rosa' chipset) do not support 4 GB RAM but have 3 GB as max. My current MBP 17" (Model ID 2,1) is such a 3 GB max model.
    0
  • Sean321
    [quote="Paul_E" wrote:
    [quote="Sean" wrote:
    Is there any way I can assign only 2gb to CO4.6 from the system side? everything else works fine... so I know it's not bad memmory modules

    Unfortunately that conclusion appears to be false more often than not. Even if only one application crashes (after a memory update) and many others are running fine, it can still be a bad memory module.

    Note that in some older MBPs (typically before 'Santa Rosa' chipset) do not support 4 GB RAM but have 3 GB as max. My current MBP 17" (Model ID 2,1) is such a 3 GB max model.


    Nope... both these are 4gb models, and both test fine on memory (had the istore techies run diagnostic on it)

    You said on the other "crashes" thread that there is an issue with more than 2gb... is this still the case in 4.6 (your old thread referred to 4.5.2)
    0
  • Paul Steunebrink
    [quote="Sean" wrote:
    You said on the other "crashes" thread that there is an issue with more than 2gb... is this still the case in 4.6 (your old thread referred to 4.5.2)

    Not sure this has been solved. It is regarded as an OS X issue but I read in a statement from Phase One they are working on it.
    0
  • Sean321
    [quote="Paul_E" wrote:
    [quote="Sean" wrote:
    You said on the other "crashes" thread that there is an issue with more than 2gb... is this still the case in 4.6 (your old thread referred to 4.5.2)

    Not sure this has been solved. It is regarded as an OS X issue but I read in a statement from Phase One they are working on it.


    When you say "an OSX issue" do you mean a CO issue only on OSX (not windows?) or OSX in general?

    I have found a quasi-workaround for this... I open up Photoshop, and a few large TIFF files in PS3, then launch CO4.6. It seems to run without too much trouble then... still faster than with only 2gb on board, and I have not had it crash when running it with something big in the background.
    0
  • Paul Steunebrink
    No, just an OS X issue 😉
    Sorry, not details available.
    0
  • Sean321
    [quote="Paul_E" wrote:
    No, just an OS X issue 😉
    Sorry, not details available.


    Hmm sorry don't buy it... all those guys out there with their 8gb and 16gb towers... there would be a lot more on the net... all I could find at apple insider was this quote:

    "With Intel's "Santa Rosa" platform, Apple's Core 2 Duo machines gained chipset support to internally handle 8GB of address space. This allows Santa Rosa Macs to shove MMIO up into the high end of the space and reclaim all of the addresses below the 4GB mark, making the full amount available to the system. No version of 32-bit Windows supports this, and conversely, there is no 32-bit version of Mac OS X Leopard, so the "where is my full 4GB?" issue is now a Windows-only problem going forward."
    0
  • Paul Steunebrink
    Sean,

    I did a search on the forum:
    In http://phaseone.com/HOME/Content/Suppor ... 20-%20Main you can read that the firewire/2GB issue that existed in CO 4.5.x is resolved in CO 4.6
    A previous discussion on the topic can be found here viewtopic.php?p=25653#p25653
    More you will find when you search the CO4/Mac forum for 'RSIZE'.
    0
  • Sean321
    Paul...

    Thankyou for all your help, but I am starting to lose faith in this software... it's just going backwards. I didn't shoot tethered, I just opened the program from boot-up. and it crashed. It crashes randomly and under different circumstances.

    I honestly can't see that the "solution" for a product such as this is "remove your RAM" (This product is supposed to service digital backs that shoot 50+mp) or remove all other apps from start-up. delete files, etc, etc...

    After rumaging through the forum, I have only to conclude that there is some really shoddy programming going on with serious memory leaks, and blaming it anywhere else than on the programmers is just ludicrous. Not one other program I use on the mac has struggled with RAM issues, software that runs for days and generates files up to 8gb in size.

    After two weeks of struggling with this software, I am ready to search elsewhere... I am very frustrated at this point, and I really hope that somebody that can sort this out actually finds out about the user complaints.

    Thanx again for trying to help.

    [quote="Paul_E" wrote:
    Sean,

    I did a search on the forum:
    In http://phaseone.com/HOME/Content/Suppor ... 20-%20Main you can read that the firewire/2GB issue that existed in CO 4.5.x is resolved in CO 4.6
    A previous discussion on the topic can be found here viewtopic.php?p=25653#p25653
    More you will find when you search the CO4/Mac forum for 'RSIZE'.
    0
  • Mikkel Selsøe
    Have you tried to remove your preferences and session files etc? I believe there is a knowledge base article on that somewhere.
    0
  • Sean321
    [quote="Mikkel2" wrote:
    Have you tried to remove your preferences and session files etc? I believe there is a knowledge base article on that somewhere.


    Even though these are new instalations, I have done that, and every other major suggestion made on these forums, and found elsewhere on the web.

    Another photographer contacted me about this as well yesterday, crashing his MBP 2.5 repeatedly after upgrading yesterday...
    0
  • Mikkel Selsøe
    Strange. I guess next step is to open a support ticket if you have not already done so.
    0

Post ist für Kommentare geschlossen.