Final Cut Pro X crashes constantly with unique error.

Could this help?

http://www.fcp.co/forum/4-final-cut-pro-x-fcpx/4220-lots-of-com-apple-helium-ren der-queue-exec-unit-gpu-crashes-after-update-help

Could be, or maybe some bad RAM or VRAM??

Here is where you can verify the card.

http://support.apple.com/kb/HT4664

Digital Rebellion's Pro Maintenance Tools has a Crash Analyzer. You could download a trial version and see what it tells you.

Otherwise, since inevitably you'll want the most current version (10.0..7) I'd be inclined to use another one of DR's products, FCS Remover, to uninstall 10.0.6 and download the new version. Run repair permissions in Disk Utility afterwards.

Russ

I have this same exact crash - except mine happens about 20% of the time when I adjust any parameter (ie opacity or a plugin ) of a clip that is playing IF any currently playing clip has a motion effect applied to it. Any motion effect - even ones I created.

Happens on OS X 10.8.3 on two different macbook pros! - one from late 2011 and one from early 2008. On the new machine I have also installed a brand new 10.8.2 system on an external drive with only FCPX installed and also get this crash when booted from that.

Lack of RAM should not cause a crash - just slow things down - but no lack here - 2008 mbp has 6GB and new mpb has 16GB.

Otherwise these machines are rock solid. I use (or have used) them extensively for performing music/interactive video on stage where everything must work… or else.

On the 2011 machine I forced the use of the integrated graphics for FCPX instead of the real graphics card. Also got the crash then.

I tried with clips imported from a panasonic GH2 and from my iPod Touch. Both caused crashes, so its probably not my video clips.

I did not have this problem in OS X 10.6.8, which i was on until a few weeks ago.

Tried running the trial of Digital Rebellion's Pro Maintenance Tools - here's the output:

Motion Effect

This crash appears to have been caused by a Motion Effect.

Suggested Actions

• Use Housekeeper to run a Comprehensive clean.
• Remove third party filters from clips, or use Plugin Manager to disable them completely.

Relevant Line

2 com.apple.Motion.effect 0x000000010c41fd05 -[FFMotionEffect newImageAtTime:duration:withInputStream:context:downstreamPT:channelOffset:roi: ] + 885

Report generated by Crash Analyzer in Pro Maintenance Tools

So I ran their comprehensive clean. Didn't help. But then again how could it? - a new totally clean system exhibited the problem.

I can't think of any common thread behind all the machine/OS combinations besides:

• OS X 10.8.2 or 3
• FCP X 10.0.7

Unfortunately I think i just trashed my zip copy of the last verision of FCP X to test, which i tend to keep around for a while when a new version comes out, but as 10.0.7 was fine on 10.6.8 which I was running until recently, I trashed 10.0.6. Is there any way to get older version of software from the app store?

Thoughts? Sounds like a genuine bug to me - the amount of different configurations it happens in. I don't know why everyone isn't having/complaining about this problem.

this error of yours is 100% re-createable if one inserts an effect and tweaks its parameters while FPCx is playing back in the timeline...

This CAN also happen when adjusting FCPx's internal color board effects..

I have yet to see this error while merely booting FCPX...

I would submit this problem to FCPx feedback and the team look into it....

Update FPCx to 10.0.7 and OS X 10.8.3 and see whether that cures the ailment.

I submitted this crash to apple FCP X feedback a few days ago. If the others of you who can reproduce it please do so also, that would be great. If apple releases another FCP X update without fixing this, it would be a real shame.

Note: I found the copies of FCP X 10.0.5 and 10.0.6 I had saved to test. This crash happens in 10.0.6, but not in 10.0.5. 10.0.6 seems to have included changes to motion effect usage or libraries or something, also projects needed to be updated between 10.0.5 and 10.0.6.

Opening and re-saving motion templates with the newest version of motion (ver 5.0.6 - which corresponds to FCP X 10.0.7) definitely produces different .moef files (which are significantly smaller) but does not seem to help the crashing problem during playback.

Also Note: the crash is not just adjusting plugin parameters - it also occurs when adjusting standard parameters of the clip such as opacity of the clip or any other clip that is playing has a motion effect applied.

Since I discovered this bug and know that the workaround is just to pause whenever i want to adjust a parameter and then play when done adjusting, things have been OK, except I'm so used to being able to adjust on the fly that I often still do it out of habit and crash the program 😟

I could (if it were still, like, 1999) understand if Apple didn't want to allow realtime adjustment of parameters during playback - its a complicated thing to code I'm sure - but if that was the case they should lock the user out of doing it, rather than letting them crash the program all the time.

Yes! 10.0.8 is out and appears to fix this crash issue. Thanks Apple.