With a Mac Pro 2x2.8 GHz having 14 GB Ram FCP-X is the only application from Mac that I have ever run which can and does regularly trash my system.
I am running iCleamMemory too - not so much because I am paranoid about memory, but it's an interesting way to watch the memory leaks in FCP-X.
As for crash reports - I find they are some what varying. It may crash when I add text, when I add a new Transition, when I try and crop a photo, when I try and rescale the time line --- perhap even when I am simiply breathing.
I have found that in some cases it gets stuck on one particular photo (I am working with slide shows more than video), and if I can delete the problematic photo then I can re-add it and get beyond at least that issue.
Yesterday I had the worst of all crases yet - not sure if anyone else has seen this, but have not found a posting about it.
I didn't get a crash report, or any other notification - my screen simply went blank. The computer was entirely non-responsive. Only option was to hold the main power button down. Back with some other applications I did once or twice get that grey screen that basically bespeaks a kernal pannic and tells you that there is no option but to power down - but this total loss of the screen and control - wow, that was new.
Upon rebooting to my horror I found that the project I had been working on for the past 4 weeks was GONE. Attempting to select it from the Finder got me the terrifying message that it was corrupt.
Time Machine had captured it earlier in the day, but the initial attempts to revive that wasted an hour for each recovery and had isseus where the recovery failed as well... no idea why. Disk Utility reports that the Time Machine volume is fine - my best guess is that with the regular and un-predictable crashing of FCP-X it dumped during a backup and that created something wrong in the record.
Restoring from a few days ago finally worked - but also lost a lot of work product.
So - it seems a good idea to insure that now and again I have actually shut down FCP-X and then forced a Time Machine Backup that I know to be healthy.
The other thing I have opted to do is to start creating copies of my project - not to work with them, but to have them as safeguards against the fear of loosing something that I have spent weeks developing. Sure, it eats up disc space - but had I been doing this earlier, I would not have been in nearly a state of panic as I was yesterday.
Really surprized at how long it is taking Apple to get even one patch file out for this. If it was something inate to my system and configuration that would be one thing, but there seem enough others experiencing the same thing that I don't believe it's just my luck with my system.
Truly hoping not to see the smoking hole crash again - and hoping to see something from Apple or another creative sole sheading some light on how to fix some of the issues here.
Cheers -