Trim Function Crashing FCPX

I am experiencing a lot of crashes and in particular when using the trim function. When making a simple trim too often the program will crash. Running 10.2.1 on new MacPro with dual Thunderbolt monitors. Also using G-Tech EV Raid with 1 TB drives for editing and OWC Dual 3TB drive for backup. Would love to solve this issue.
Thank you
Scott Wilkinson
Fresno, CA USA

Hi Scott, welcome to the forum.

The first thing you should do when you have unexpected crashes while trimming is to delete your FCP X preferences. Close FCP X and launch it again while holding the ALT+CMD keys pressed down. You will get a message asking if you want to delete your preferences, confirm and let FCP X launch. Then open your project and see if this solves the problem.

If this doesn't help, the next thing you should do is disconnect the second display and see if this solves the issue.

If you still get the trim crashes after these tests: create a new admin account and launch your project with that account.

Please keep us posted on the results.

- Ronny

Unfortunately I'm also seeing a lot of this. On multiple projects too. The trim and slip functions will often trigger a crash. It doesn't break anything but it's getting really annoying because of how much it happens.

Hey Braden,

Try the suggestions above. If none of these help, this might be specifically related to 10.2.1. In that case call Apple support to see if they have any solutions, or file a bug report.

- Ronny

Ya, I've tried various things. I'll try preferences. I can't remember how recently I did that. I've definitely sent feedback reports into Apple. Though they hopefully have gotten the hundred crash reports that have been generated. This has been the buggiest release of FCP X in my experience with a variety of issues. Hope they're working hard on a stability update.

I feel your pain. The crash reports are certainly helpful for them to find out what's wrong. Delete prefs and certainly do the "new user" test. This is an important factor for narrowing down a software problem.

10.2 has not been really bad for us. The performance gains we get make up for the little (and bigger) annoyances that often come with every major change under the hood. In our experience, 10.1 was the buggiest version ever. But after two updates everything got smooth again. Let's hope we will see the same now.

- Ronny

Could you share details of your media and computer specs. Anything in particular that you can point to that's repeatable.

I have seen this also on a recent project using Sony XDCAM HD422 XAVC-L 1280x720 59.94 footage. Editing 16 different video presentations ranging from 30 min to 2.5 hrs in length. Trimming and slip edits caused at least 15 FCPX crashes over the 4 days of editing. These were issues on both primary and secondary story lines. We usually edit XAVC-I. According to crash log reports, FCPX hasn't crashed in months other than the recent past few days editing the above project. Deleting prefs did not help. Did not try disabling second monitor (we actually have 3 connected) because we never had this issue before.

Tom,
Using MacPro, Late 2013, 3GHz 8-Core, 64GB Memory, SSD HD, running two Apple Thunderbolt monitors. Shooting with JVC HM100 on 32GB SanDisk Extreme SD Cards. Running FCPX 10.2.1. Also using OWC Mercury Elite Dual Pro-3TB and G-Technology G-Dock ev Raid with Thunderbolt. Reset my preferences and it is a little better, but still getting unusual amount of crashes, typically 4-6 in an 8 hour work day.

I will also add that our IT department had a bit of an accident with this computer when we took delivery. As they were making it ready to bring to my edit suite they picked it up by the top/shell and the bottom fell out. The SSD was toast. Apple was super great and replaced the SSD "no charge" even though it was our fault. How is that for customer service? I think the guys at the local Apple store felt sorry for our IT dude. Needless to say I was sad that I had not even made a single edit and we were already sending the unit in for repair. Sooo, I am not sure if this little incident is now showing up in some strange way with all these crashing issues. I want to think it is more software related, but one can't help but wonder.

Scott,

Can you create a new admin user account to test if you still get the crashes when working with a new user? The fact that deleting the FCP X preferences solves the issue but only for a while, makes me suspect there is something wrong at a different level.

- Ronny

Hi All
Crashing and total system freezes is being reported on many forums.
I've been helping someone on the Apple forums and he went through every possible fix, no love. This was on a new rMBP He eventually got a brand new replacement laptop from Apple. Still crashing.
Now he is reporting that he thinks it is related to "wireless" devices. Not sure this is really it, but hoping folks will report if they are using any wireless keyboards, trackpads, mice, etc… If you are, would you please remove them, even turn them off and only use wired devices and see if you still get crashing / freezes?
I'm wondering if this could be related to using "discoveryd" for networking. Apple has been having lots of issues with discoveryd and in latest 10.10.4 Beta has switched back to using rDNSResponder.
Just thought I'd throw it out there.
But it seems to be related to FCPX as it is not occurring in other apps.

Hope this helps, Greg

FWIW I was reading a Blackmagic forum and there were some discussions there about corrupt clips causing FCP X crashes. Apparently even though they were not using a corrupt section of the clip, the clips in question were causing problems. Perhaps that's an area to explore?

As far as wireless devices, I've been using a Magic Mouse daily and have not seen this particular behavior.

After every update we see reports of people who have different kinds of problems, that does not necessarily mean there is a widespread issue. So I think we must be careful with this.

There are a few known bugs in 10.2/10.2.1, but more frequent crashes don't seem to be a general problem at this time. Of course it is annoying for the people who do have these crashes and I hope we will be able to narrow it down to something specific.

Just to be sure it's not a general issue I have asked the lead editor of a television company where they have +30 FCP X seats if they had seen any crashes since 10.2.1. They do some very heavy editing with lots of trimming, so I think if there were a problem they would be the first to notice it. I have received his reply a few minutes ago, I'm sure he won't mind if I paste it here:

"All FCPX systems are running 10.10.3 and FCPX 10.2.1 now. We have just updated a big series to 10.2.1 this Thursday. So I'm sure they haven't experienced any crashes. Otherwise I would have heard. I myself have been on 10.2.1 some time now and I haven't had any either. To me 10.2.1 feels like 10.2. I'm not even sure I can feel anything different. All editors use wired keyboards and wireless Magic Mouse. The only problem I have experienced with this was a couple of weeks ago when all of a sudden I couldn't get access to my iMac if Bluetooth was on. Since then I have only been able to use the old wired mouse. I have been thinking about doing a complete reinstall but haven't had the time to do it yet. "

- Ronny

if you haven’t already, you should report this to www.apple.com/feedback/finalcutpro.html

is the crash more likely to occur when trimming while showing scopes?

I'm having the same issue - crashes with error report every time I trim.

I thought it was my plugins so I removed them one by one, which sometimes worked but then it started crashing all over again after a while.

But Emily seems to have spotted something with the scopes. I turned off the scopes and now it's not crashing!

What's strange is that when I turn the scopes back on it still doesn't crash.

We'll see what happens over the next few days. Maybe I can even reintroduce some plugins...