Tom - Look under 'Graphics and Video support' - http://support.apple.com/kb/SP544
Thanks for the update which is genuinely informative for many people with this problem. Comments like this help us to move forward. I'm still using the slower graphics card. I am however using a Firewire 800 external drive and as others have posted, this too seems to be a problem. Additionally I use optimised media.
Keep the updates comming, it's all constructive.
There is a new update - 10.0.7
It makes not mention of any fix to the problems people are suffering on this thread, that being - crashing whilst rendering when using no third party effects and a suspected problem with some graphics cards and/or firewire 800 external drives.
It does however fix the issue with third party effects. I don't use any.
All that said I think it's worth a try and so I'm going to update.
Who's with me?
No, that didn't work. Seriously, seriously f**ked off.
FCPX 10.0.7 stalled after 35% of a render, then quit. This caused the Mac to freeze after about a minute.
To define freeze, I can move the cursor but clicking delivers no results.
I then had to Force Shut Down the Mac.
I was using the faster graphics card in my mid 2009 MBP 3.06 Ghz, I'm sure if I use the slower graphics card it will work again.
What is going on??
Can any one else confirm whether the update worked. I'm interested in people who DON'T use third party effects.
I updated to 10.0.7 the second it came out! I did the same with 10.0.6 and regretted it the moment I did. But I figured things can't get worse than the previous version so I upgraded again. Now, I haven't had heavy work load since I updated but I have not yet had a serious crash. I did have the bug with the color mask not showing up and requiring a restart again but not the same instability I had with the 10.0.6. That bugger was a disaster! I have never been more frustrated at Apple than after I downloaded 10.0.6! I feel like things have improved and now I can use the program once again! I will report again if this version starts to screw around! So far, so good though!
Jeff, did FCPX crash while anything specific was happening? or did it just crash instantly? I've been very stable for the longest time in FCPX 10.0.6 and it just began crashing whenever I click the Background Task (to expand the background task details) and it's a weird crash - an instantaneous blue screen and back to my desktop in the blink of an eye!
I have turned background rendering off.
I get crashes whenever I render. It usually renders between 10 to 40% and then crashes. The crash then wits FCPX after about 30secs or so. Then tha Finder becomes unresponsive after a few minutes and I have to Force Shut Down the Mac. So it crashes only when I render.
I can confirm that switching to the slower graphics card on my mid 2009 MBP 3.06 Ghz solves the problem. But of course this is far from satisfactory.
I've read this entire post. It's overwhelming! I hope this gets worked out, and to that end I want you to know some stuff on my end at my fulltime video job for VailResorts at Keystone: We purchased a 12-core Mac Pro and my manager installed a SSD for the "Macintosh HD" - so OSX 10.7.5 and all apps reside on this drive.
We have not gone to Mountain Lion because so much of our past work is on legacy apps such as FCP7 and we are still needing to be able to open some of those projects.
We purchased FCPX, Motion and Compressor and after using all of them without any major issues, (there were a few little issues - namely "memory leak" where available RAM would go off-line the longer FCPX was open and would not release it until I quit and restarted, etc.)
I did the 10.0.7 update and here at work, no real big issues; we do not have any third-party software, just FCPX. However, I am not on a Firewire hard drive, all my projects and events are on a 16TB SAS RAID. A hardware RAID controller card busses all my data back and forth via four SAS cables. I have 32GB of 1333MHz RAM installed.
At home, however, I have a 2010 Mac Pro 2.8GHz Quad Core, and 8 GB 1066MHz RAM and a smaller but similar hard drive setup: CalDigit Hardware RAID controller card to a 4TB miniSAS RAID. I haven't yet updated to FCPX 10.0.7, but I did the 10.0.6 update. I hadn't used it extensively until last Friday when I began importing to a new Event from my USB RocketFish CF card reader. Things were going fine as usual then I clicked on the Background Task icon next to the Timecode under the viewer and both my screens flashed blue and instantly I was back up with my desktop - FCPX was closed and my Canon Utility opened as though my Mac Pro only just detected the card reader. It was shocking. Worse, now my fan comes on full-blast in a way I've never heard before. I'm very freaked out about it. I have no idea what is going on.
At work (Keystone) though, FCPX is still working well, although I haven't imported anything since my last big project before updating to 10.0.7. Even this morning I tried clicking on the Background Task several times and everything seems solid. On a totally unrealted plus, we're getting snow!!!! Lot's of snow!
I was having big problems too after upgrading to 10.0.6. But after purchasing a Tempo Express Card/34 and using E-SATA for my G-Tech RAID, I've only had a little weirdness. At least not the continual crashing and FCP X locking the whole computer up.
Then I upgraded to 10.0.7 and all the really bad stuff started happening again so I uninstalled 10.0.7, re-installed 10.0.6 (using Apples instructions) and have only had a few crashes, albeit one that required a hard shut down. At least it's workable. I've exported HD video to both Vimeo and YouTube. I think my MBPro is the same year as yours.
yet another... wrote:
...Things were going fine as usual then I clicked on the Background Task icon next to the Timecode under the viewer and both my screens flashed blue and instantly I was back up with my desktop - FCPX was closed and my Canon Utility opened as though my Mac Pro only just detected the card reader. It was shocking. Worse, now my fan comes on full-blast in a way I've never heard before. I'm very freaked out about it. I have no idea what is going on...
You've had a low-level crash, but not a kernel panic. The power manager (that keeps the fans down) has stopped controling them, so they go up to full speed. This is a normal fail-safe, so you CPU's and other stuff does not overheat!
Reboot, and you should be back to normal.