FCPX crashing a lot

[machenryr]

I could assume it might be something else but the crashes only started when I started working with FCPX. Has anyone else noticed this? I have several apps open which I shouldn’t do. I’m going to try closing them. Just wanted to know if anyone else has seen this. 2019 Mac Pro 16 core. 160 GB. Latest FCPX.

 

[casperes1996]

Hold on are you saying that Final Cut is crashing or that the system is crashing entirely? What's reported as the reason for the crash?

 

[AZhappyjack]

I could assume it might be something else but the crashes only started when I started working with FCPX. Has anyone else noticed this? I have several apps open which I shouldn’t do. I’m going to try closing them. Just wanted to know if anyone else has seen this. 2019 Mac Pro 16 core. 160 GB. Latest FCPX.

2018 Mini 3GHz i5 1TB SSD 16GB RAM running Catalina (10.14.6) and FCPx 10.4.8. I edit 1080p video all day at least 3 days per week... ZERO crashes of FCPx, macOS or any app. Typically have ForkLift, BBEdit, Safari, Firefox and Messages open concurrent with FCPx. There's also the occasional use of Motion, also concurrent with the others... and I have tons of FCPx plug-ins installed - mostly from MotionVFX and Pixel Film Studios...

Tell us about your workflow... what are you editing? What are you doing with FCPx?

 

[machenryr]

Hold on are you saying that Final Cut is crashing or that the system is crashing entirely? What's reported as the reason for the crash?

I’m not sure. From what I can gather parallels was mentioned. Sometimes the whole system crashes. Other times like RIGHT NOW spinning beachball allows me to force quit. Earlier I had to reboot Mac. These are kernel panics with Mac reboots.

 

[casperes1996]

I’m not sure. From what I can gather parallels was mentioned. Sometimes the whole system crashes. Other times like RIGHT NOW spinning beachball allows me to force quit. Earlier I had to reboot Mac. These are kernel panics with Mac reboots.

I've had Final Cut crashes, but it's been like a year and a half since I've last had a kernel panic.

When you get a kernel panic again, I'd be interested in reading the log of it to see if I can figure out what's causing it

 

[machenryr]

2018 Mini 3GHz i5 1TB SSD 16GB RAM running Catalina (10.14.6) and FCPx 10.4.8. I edit 1080p video all day at least 3 days per week... ZERO crashes of FCPx, macOS or any app. Typically have ForkLift, BBEdit, Safari, Firefox and Messages open concurrent with FCPx. There's also the occasional use of Motion, also concurrent with the others... and I have tons of FCPx plug-ins installed - mostly from MotionVFX and Pixel Film Studios...

Tell us about your workflow... what are you editing? What are you doing with FCPx?

I’m not a experienced FCPX user. But I’m doing something very easy. Maybe wrong? Three clips. Two Cams and one audio. I’m in a project after doing a multicam. Now I’m putting in text. Sometimes it just kernel panics. Towards the end of this 12 minute video every time I drag a text above a clip I get a spinning beach all. Then it goes away mostly. But this isn’t a lot im asking CPU wise. My 16 core 160 7,1 should handle this fast.

I have Firefox, Pages, Numbers, QuickTime and a few other things open. I had parallels and windows 10 with two small apps open in that. Hm. Now the share at Apple 720 failed to save.

 

[AZhappyjack]

I’m not a experienced FCPX user. But I’m doing something very easy. Maybe wrong? Three clips. Two Cams and one audio. I’m in a project after doing a multicam. Now I’m putting in text. Sometimes it just kernel panics. Towards the end of this 12 minute video every time I drag a text above a clip I get a spinning beach all. Then it goes away mostly. But this isn’t a lot im asking CPU wise. My 16 core 160 7,1 should handle this fast.

I have Firefox, Pages, Numbers, QuickTime and a few other things open. I had parallels and windows 10 with two small apps open in that. Hm. Now the share at Apple 720 failed to save.

SOMETIMES the beachballing and apparent freezing or really laggy response can be caused by having background rendering on. Go to Final Cut Pro > Preferences > Playback ... and make sure BACKGROUND RENDER is unchecked. That should help...

Not sure about the kernel panics... what's the machine? Is it a newer Mac with a T2 chip? There are plenty of threads about T2 chip issues and kernel panics... as far as I've seen, there is no definitive issue or solution... kind of a hit or miss thing. Do you see these kinds of issues when Final Cut Pro is not running?

 

[machenryr]

Thanks. I do not see these issues when FCP isn’t running. I’ll try your suggestion. The rendering has failed three times in a row.

Here’s a weird thing. I have two Camera angles. The 2nd angle when blank about 10:00 in. Beachball goes nuts around that point. The details on the failed share indicate that as the problem. So now I trimmed that area out and am trying it again.

 

[machenryr]

It worked this time. I had to edit that blank section out. It rendered.

I’ve had some issues with this Mac Pro since I got it in late December. Early adopter. 2019 7,1 16 core 160 GB. What gives?

 

[casperes1996]

It worked this time. I had to edit that blank section out. It rendered.

I’ve had some issues with this Mac Pro since I got it in late December. Early adopter. 2019 7,1 16 core 160 GB. What gives?

Very strange. I worked with multi-cam clips just a few weeks ago and no issues with areas where one of the angles is blank. May be a specific codec or something; I'd probably recommend sending Apple feedback about the crashing.