[Robert Salsbury]

Hi

No solution to offer, sadly, only a me too.

What I can add is that I’ve noticed that BEFORE you’ll get green frames, FCP dumps a lot of messages like this in the console:

11/18/09 9:37:34 AM [0x0-0x3a03a].com.apple.FinalCutPro[425] Final Cut Pro(425,0xa00ad720) malloc: *** mmap(size=268439552) failed (error code=12)
11/18/09 9:37:34 AM [0x0-0x3a03a].com.apple.FinalCutPro[425] *** error: can’t allocate region
11/18/09 9:37:34 AM [0x0-0x3a03a].com.apple.FinalCutPro[425] *** set a breakpoint in malloc_error_break to debug

and by a lot I mean it’s repeated a few thousand times.

If you can an eye on messages in the Console application (“Console Messages” section) you can see when you need to reboot. On some systems with large projects, that may be more often than you like, but I’m managing ok, keeping project file sizes as low as possible.

I also zeroed out my stills cache – set it to ZERO, so that FCP would have as much of the RAM available to it as possible before getting wacky. No real time stills animation, but that’s not a problem for me on this show. And render to ProRes rather than XDCAM for sure.

-Robert