Can’t Work on Project – CRASH

[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!!

[Vic Mmm]

FCP crashing on opening project.

This is my situation, on Final Cut Pro X 10.2.1 OSX 10.10.1 I could open FCP but if I clicked certain projects it would crash.

I tried several methods before finding one that worked. What didn’t work:

1) trashing preferences
2) opening project in OSX safe mode
3) highlighting corrupt project with arrows, File > Export XML, Closing FCP, File > Import XML

The 3rd option actually made things worse as in made the project that opens by default corrupt, forcing me to open FCP with no default file present then choosing the library to open.

This is what did work:

First open the library and move the curser with the keyboard over the corrupt project then Duplicate Project as a snapshot (shift command D). Make a many copies of this, as it will take many times to get the next instruction to work. It took me a few dozen times before getting the hang of it.

In a non-corrupt project in the same library make an edit (like a transition effect) that forces some render to show in progress, then double click the corrupt project, and QUICKLY click the timeline and select all (command-A) and delete the whole project. This should cancel the render that was corrupting the opening. Now you can redo the deletion to bring it all back and it won’t crash like it did before.

Hopefully this helps someone else, as nothing else online was working for me. 🙂