Effects Titles lock up FCPX / 10.8.2

What are the complete specs of the machine? Have you reported it to feedback? Can't reproduce it on my 2012 MBP with the current software and OS.

I just received this mail from Apple Support (or is it FCPX support) after using feedback yesterday.

So I think Apple is indeed working on this issue at the moment.

Now I'll send them my crash log...

Hi,
This is Noah from Apple. We recently received your feedback regarding Final Cut Pro X. You mentioned Final Cut Pro X crashing with new 2012 iMac. If you're open to it, we'd really appreciate your assistance in diagnosing the issue.

Can you please send me your crash reports? Here's how: In order to obtain a Crash Log, you will need to open the Console application. Console is located in the Utilities folder which is inside your Applications folder.
When you open Console, you will see a list in the left-hand section of the Console window. Choose Files > ~/Library/Logs > Crash Reporter > Final Cut Pro. Click on the most recent crashes. Then, click on the File menu and choose "Save As...." Save that file to your desktop or somewhere handy in order to attach it to your reply email.

Best,
Noah

Yep, already sent them a more complete dump of logs to the person following my case (i.e. ran a script which dumps them all and FTPs them to him and he checked them while I was on the phone). I don't think there's a lot in the logs however as I don't /think/ FCPX or Mac OS even realise anything has gone wrong until you force switch off, so the logs only seem to report an incorrect shut down. However, being able to tell them that by just creating a project, add a place holder and the pixie dust title and try to render will always cause a crash will ensure that the FCPX engineers will be able to set it up to trace what is happening and hopefully fix it. We just have to hope that the fix is something relatively small or else I could see this taking months for them to regression test any patch.

It certainly seems that Apple FCPX team have taken on board that its definately an issue and not individual's config/file problems, so I'm sure it will be being looked at urgently, particularly as it's their latest "flagship" product line with one of their prime applications. The press fall out otherwise is likely to explode quickly.

Note - I've found that the lock up does not actually seem to mean the OS and the program have completely crashed as I just had a case where the audio for the project kept playing for a few minutes until the end while everything had seemingly locked up.

What I think this means is that as long as you leave it long enough for the background auto save to kick in before restarting the machine, no work will have been lost - but I can't guarantee that! Since I've started waiting 3+ mins before powering off though, I don't seem to have lost anything I'd done. Just a suggestion to maybe help people work around this until its fixed.

Same problem here: import PNG 1080p in size and add text ontop - crash crash reboot machine, reimport file, crash. Very annoying and basiclly shat on my plan to have some animated text on a png background for the video I'm working on. Apple?

First thing to do when simple actions crash FCP istrash prefeences.

Russ

I appear to of fixed the problem by editing the title in proxy. When I switch back to high quality crash. Will try the pref delete but first let me see if I'm getting same problem on my MBA.

Appears to be hardware related - APPLE!

I removed pref files also repaired permissions but still crashes but on my mac book air I do the same thing and don't get a crash. HD4000 vs Mac Min AMD card appears to be the issue unless I have a plug-in that is causing the crash?

Workaround is to do the text over the png background using proxy, strange. Tries to use TIFF too but also crashed.

If the computer is crashing not just the application you need to take the system to an Apple store or service technician.

No the computer is fine, just FCPx crashes.

Look through the FontBook and make sure every font is good and none of them are corrupted.

Don't see any corrupted fonts but I do get 53 minor problems - mostly duplicates I think.