[Charley Holland]

Hello,

For what it’s worth, I had kinda the same issue today. After much messing about I was able to fix the problem in my case. Firstly I had to stop Background Rendering. I noticed FCPX was doing this frenzied rendering, which quickly soaked up all the memory, causing an application memory alert. So, stopping background rendering allowed me to investigate.

Secondly, It was only in one project that the frenzied rendering was occurring.

When I tried to export (share) the project, I got a fail message, which handily gave me the frame number that the export crashed at. Zooming all the way in to the timeline, I discovered a few frames of a movie that were unrendered and would not render manually. “Revealing In Finder” and right click opening with Digital Rebellion’s QT Repair app gave me the diagnosis of very corrupt!

I remade the video file, and in doing that was alerted to the possibility that Perian may have caused the corruption in the first place. I disabled that, laid up the new video, deleted the old and problem fixed.

I could even turn background rendering back on.
This thread helped me enormously. Thanks to everyone!!