The Final Cut Pro X CRASH Thread

Mine crashes pretty regularly. Not everytime, but frequently enough to be a real pain

I recently transcoded my footage using Mpeg Streamclip into ProRes422. Had no issues at all, no crashing, fast response rate. Give it a go.

My crashing habits seem to be format/import related. I dont trust the built in 'optimzied' transcoder.

Some projects are good, others blow. Got to be a format issue???

Notes:

- Exported ALL footage from a flip HD (using Flipshare) into 1 big *** ProRes422 at 100% quality (had to try) using Streamclip.

- Chopped it up in X

- So far so good.

Anyone else?

Never mind... just started crashing again with effects. sorry for the flop.

**** IT I HAVE THE SAME PROBLEM....from two days.....TERRIFIC. Even if FCPX is the only one app that i started up. (I have MBP with 8gb ram)

Process: Final Cut Pro [2455]

Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro

Identifier: com.apple.FinalCut

Version: 10.0.1 (185673)

Build Info: ProEditor-185670300~1

App Item ID: 424389933

App External ID: 4138831

Code Type: X86-64 (Native)

Parent Process: launchd [225]

Date/Time: 2011-10-21 19:17:47.063 +0200

OS Version: Mac OS X 10.7.2 (11C74)

Report Version: 9

Interval Since Last Report: 35896 sec

Crashes Since Last Report: 11

Per-App Interval Since Last Report: 205 sec

Per-App Crashes Since Last Report: 11

Anonymous UUID: AA352EED-425F-4F47-AFF6-2643E451F433

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

PLEASE HELP ME

I have exactly the same problem as everyone in here. I've got a 13" MacBook Pro from early 2011.

Intel Core i5 2,3Ghz (Up to 2,9Ghz per core with turbo-boost), 2 cores, 4 threads.

Intel HD Graphics 300

4GB Ram

I am seriously annoyed by the fact that I have a 1200$ worth laptop that is working like absolute ******** in Final Cut Pro X, after I updated to Lion. Rendering is quite fast, and fine (Snow Leopard was still faster).

I can't believe that for the price, you get such crap performance, as for the same 1200 bucks I could have gotten a hardcore gaming PC with 8 cores, and now I'm getting into this crap.

How is this possible Apple? I've been people having a 10 THOUSAND dollars worth Mac Pro (24-core 48GB RAM...), which I believe is seriously impossible to have that performance. Come on! Get us a fix fast!

Lots of crashes here too. Plenty of memory. 10.6.8 Mac Pro. Add to the crases that FCPX doesn't save text in Title templates and you've got a huge "do-over" problem everytime you open.

Adobe Premire is bending over backwards to take avantage of these problems offering guidance for transitioning and even a FCPX keystroke shortcut menu item. If I thought I could get a refund from Apple, I'd make the switch.

There are enough postings that these problems would have been fixed if they weren't insurmountable.

We may have a problem!

18 pages of people experiencing massive crashing. Apple can we get a response please????

Im running lion on a brand new mac pro 8 core with 8 gigs of ram.

If the program can't run on this thing then what can it run on? It appears not to be compatible with Macs in general. There's no way in **** this product was tested prior to release without knowing that we would all be dealing with this. This is rude to say the leaset. You stay up all night working on edits and there is no manual save function, you have no way to know the the auto save isn't working then you call it a night at 2 am and come back in the mornig to check what you've done only to find that its all gone and nothing was ever saved. That is not only careless to release a porgram in this early beta stage but its flat out unprofessional. More than one person in the company had to have known about this and they put tyhe release date over the functionality. I love apple but if this was the apple experience I would be using

a PC. Better clean it up Apple before someone comes along with a better option. I just spend 5 grand on your pro computer and your editing software doesn't function??? Seriously????

If I bought a product like this off the internet from a company I never heard of I'd be ****** and assume it was just a rippoff but to get this kind of servivce from Apple I'm floored. Those of us that love the product and the company deserve and explanation, a fix or a full blown recall if a fix can't do the trick. If this were a product released by a tire manufacterer you would have people dying all over the highway. Speak up, we know you are reading these posts and its time to speak to your customers and take some responsability.

Maybe we should start a thread demanding that Apple responds and apologizes.

Let me say what most posters who come here with issues, looking for some help, don't want to hear.

FCP X is working for me.

Now let me try and offer some suggestions that might help.

Save Isn't Working:

There is a way to check if it stops working. If you can no longer Undo something, Save is not working. This seemed to be a big issue in 10.0.0, but it seems to be gone in 10.0.1. I have yet to see it. If you discover that it does quit working, you might be able to duplicate your project. No need to duplicate render files, just the project. Easy to do. I don't know if it works, since I havne't had this issue.

RAM:

On my system, 8GB would not be enough. I'm running Lion 10.7.2 and FCP X 10.0.1. FCP X typically takes up over 7 GB, with a kernel taks taking over 1 GB. That's with nothing else running. Running out of RAM for FCP X does seem to be an issue for some people. Should it be an issue? No. But having more than 16 GB is a very good idea.

Inactive Memory:

I don't know what causes Inactive Memory to grow, but it does. While I use FCP X I watch Activity Monitor. I open Activity Monitor, Hide it and right click it to Show Memory Usage. That way, I can easily check the status via the Dock. Inactive Memory grows to over 4 or 5 GB. From many other posts I've read, this appears to be an issue with Lion. Some users have gotten memory cleaner applications for this. I use purge, a command in Terminal. If I don't reset Inactive Memory, I will encounter issues. (at least for me)

Preferences:

Whenever you start to have issues, most agree that trashing your FCP X perferences helps. Get Preference Manger. It's free and it not only can easily trash your preference, but it can re-load them as well. Obviously re-load known good ones.

http://www.digitalrebellion.com/prefman/

Also, here's a nice troubleshooting link for FCP X.

http://www.kenstone.net/fcp_homepage/troubleshooting_fcp_x_taylor.html

As I mentioned at the start of my post, FCP X is working for me. It's not perfect. I've had it freeze. But, I've never lost more than a very small amount of changes. What I'm currently working on is broken down into 10 different projects. The single Event has 1,914 clips of 720P HD. I spend hours editing every day. I periodically export both ProRes and burn BluRay for viewing, testing and backup.

While FCP X is not perfect, it does work a lot better than what you are experiencing. I hope you'll find some of these suggestions useful.

Thanks for the input.

Concerning the "Save insn't working"

I have experienced the undo (Command Z) not working and had to carefully note the number of frames something moved so that I could manually recreate it if need be. It's not consistent but it has happened.

Concerning "Ram"

I'm running 24 GB on a Mac Pro ver. 10.6.8

I have trashed the preference just this morning after several crashes while trying to launch. I can't keep the app open. Sometimes upon opening it starts to render then crashes. Other times it indicates 100% rendered and still crashes within 30 seconds.

We need some official word or to be provided with an earlier, more stable version of FCP or a refund with which to purchase other software.

For what it's worth:

My crashes issues (on launching the Timeline) seem to be related to media and FCPX accessing that media.

Check codecs - check Preferences to make sure you are using Proxy Media if you have large or HD .mov files.

All media in the folder which was not imported through FCPX ..................

NEVER MIND. IT JUST CRASHED AGAIN! Seldom does one pay this much for total nonfunctionality.

Have you tried the trouble shooting suggestions in the link I provided?

You may have some corrupt files.

You could try deleting render files. Also, try turning off background render. That might prevent FCP X from constantly crashing so you can troubleshoot.

It sounds like you have something causing your issues, as opposed to it simply being FCP X. Even if FCP X caused an issue with your project/event/media, you should be able to troubleshoot the cause and get things back in order.

Wow! Just turning off background rendering stopped the crashes. It's been up and running now for 10 whole minutes without crashing. Should I still try deleting the render files?

Thanks for that!!

I'll go to the link you suggested.

Sounds like you might have started to pin point the issue causing the crashes.

Without knowing anything about your project ...

Any render file you delete, can simply be re-rendered.

Sounds like you are editing with proxy media, so those renders would be deleted along with any rendering done for work in timelines.

If you delete render files, keep in mind that there are render files associated with both Project and Events.

Not knowing how big your project is, you could consider deleting all render files and then turn on background rendering and watch the render process to see if it crashes, what file it crashed on. Assuming the crash is being caused by an attempt to render a particular file that is corrupt.

I think you could also just duplicate the project and select to not include the render files and start from there. Keeping your existing project in tact.

Either way, sounds like you have an issue with either a bad render file, or perhaps a bad clip that can't be rendered.

Many thanks. I did duplicate the project without rendered files. I then rendered All and it crashed at about 50%. I narrowed it down to the clip which when rendering makes the app crash. This is incredible progress and without wanting to turn you into a private tutor I have to ask you one more question.

The clip is from the same source media as other clips which render without a problem. I have replaced the clip with the identical section and it still crashes the program. What would make one clip act this way and none of the other clips from the same source?

Should I re-transcode the original media? Or just this section of the orginal media?

Thanks for any help.

What is type of clip is it? As in codec.

Are you using it natively, or do you transcode it to edit with it?