FCPX 10.0.5 crashed and logged me out

Not a fix. continues happening here in 10.6.8 and FCPX 10.0.7- has happened twice now since i last posted. Usually when queuing several clips for dominant motion analysis. Last time it happened was when i tried to open the Background Tasks window to see how my analysis was going along and suddenly - bang - blue screens and back to log in menu.

This is really annoying Apple - a user program should NOT be able to cause you to log out losing work in other software when it crashes!!!

Snow Leopard seems to be common factor with this problem.

No, it's not an OS issue. I'm running 10.6.8 and 10.0.5, same issues as others are having on my 2009 Mac Pro. My specs are 2.66GHz quad, 16GB RAM, 5870 video, and 5 TB of internal storage (5 1TB HDD's, using an optical bay slot for the 5th drive, OWC mount). I wouldn't consider upgrading to 10.7 or 10.8 as realistic or useful advice. Not all of us want Apples latest toy OS. 10.6.8 is fast, stable, and iOS junk free. Can we please work on fixing the REAL issue?? Thanks.

Anything that takes down the OS is an OS issue. Sandboxing should absolutely prevent this from happening. I don't know how extensively it was implemented in 10.6.8.

FCXP is newer than 10.6.8. FCP 7 didn't have this issue. The previous version of FCPX didn't do this on my Pro running 10.6.8. I'd say that's an application issue. Apple obviously didn't thoroughly test FCXP on anything other than 10.7/8. The fact is FCXP is an absolute embarassment, especially as it is marketed as a Pro app.

Chris says "OS 10.6.8 is fast, stable, and iOS junk free", I agree completely!

Thom

Chris - now you're starting to no longer make sense. It's irrelevant if it's on OS or an app issue. There are problems with certain Macs, OSX 10.6.8 and FCPX - we know that, Apple knows that and if it was real easy to fix, I am sure they would have by now. On my one machine that has the crash problems, I cannot upgrade to a newer OS or I'd have to uprage our SAN software too. If the SAN wasn't the issue, I'd upgrade to Mountain Lion in a heartbeat. It's a no brainer. I am running Mountain Lion on my MacBook Pro with FCPX and it works flawlessly and it's really fast.

What you label as "iOS junk" is actually the real strength of the new OS. I am talking about the OS engine you cannot see., not the interface gimmicks. FCPX no longer uses quicktime as its media engine, but AV foundation (which also runs on iPads and iPhones). AV foundation is the reason why FCPX does things so much faster, why it allows you to edit H.264 footage natively and it's all there built-into the OS. That gives FCPX a real advantage over other NLE's that have to be cross-platform. AV foundation wasn't 100% implemented until Lion.

Lion had some clunkie issues, but Mountain Lion is rock solid, IMHO. Unless you have hardware that's too old, or compatibility issues (as I do on that MacPro) there is absolutely ZERO reason not to upgrade for FPCX.

If it's so bad and it doesn't work fir you, you shouldn't use. If you're so frustrated with the application it would be better to move on to something that suits you and works better with your system.

Hi, I'm also on 10.6.8. with FCPX 10.0.7 on a Mac Pro. FCPX logging me out on different actions (clicking share, opening compound clip, sometime even right after starting the fcpx app).

Tried various troubleshootings: ie. deleting com.apple.FinalCut in user Cache folder (helped), deleting fcpx preferences in user Preferences folder (also helped). But all only temporarily. Problem keeps returning. Very annoying and counter productive.

Any other, maybe more long-term solutions to this bug?

I have OS 10.6.8 and FCPX 10.0.7. I was having the same problem you describe, but I think the problem was elsewhere other than FCP itself. After several weeks of repairs (the Apple techs replaced two sticks of memory and did an erase, reinstall, and restore on the Mac's hard drive), I found FCP works much better; since then it hasn't logged me out again.

I too just experienced this issue. For me it played out as follows. Open FCP X 10.0.7 after fresh start up. Take the project that opens and do a File/Share to export the project. IF and only IF I select Background Tasks to see the progress of the export it logs me out of the computer instantly. I log back in and this repeats. The third time I did not select Background Tasks and the process completed without a hitch.

My specs are:

MacBookPro, 2.2ghz Intel Core i7, 8gb Ram

OS: 10.6.8

I saw the mention of rebuilding the machine. Might look into that but it's a work machine so it's slightly more involved than your typical process.

Thanks to all the posters contributing their experiences.

I am convinced, it is related to FCPX, as it only happens with this app and for me after working with macs since 13 years on a professional level with countless of different apps and plenty machines and configurations, I have never ever seen such a drastic bug. it seems ironic that it appears with an app that is of apple's own creation.

is this an issue with os x 10.6.8 only or are users of os x lion versions also seeing this bug?

ps: sorry for the late reply, I have not received an update mail for the thread after your post. only now after Tembrock's post.

Message was edited by: retnuoc

btw uekral, what machine are you on?

OS 10.6.8. After computer repairs in December

, FCPX is more stable, but still occasionally logs me off.

I urge everyone experiencing this stunning bug to send feedback to Apple through their feedback link:

http://www.apple.com/feedback/finalcutpro.html

Make sure to mark it as a "bug" and not as a technical problem. It IS a bug.

When I used their feedback page, I got a response from an Apple tech person within a few minutes asking for my system info and my crash logs. So they are very aware of this bug. The more people write in, the higher it'll move up on their list of things to fix.

I think it is mostly related to FCPX Snow Leopard systems, which unfortunately might move the problem lower on their priority list. But they list Snow Leopard as a supported system, so by all means - do send them their bug reports!!!