-
FCPX Crashing my entire OS CONSTANTLY
-
Correct, I’ll be playing a sequence, and when I try to pause, I’ll see that the computer is no longer responding to any keyboard or mouse commands, including command-option-esc. If I pull the charge cord out I’ll see the battery indicator reflect the change, and the system clock keeps working. But nothing I can do lets me regain control of the computer.
retina mid-2014 macbook pro
2.8 ghz intell core 17
yosemite 10.10.3
fcpx 10.2.1 -
Ouch. If the system is not responding to command-option-esc and you are not getting kernel panic then I suspect something is wrong at the user account, OS install, or even the hardware level. FCPX pushes the hardware very hard using all cores and GPU to the fullest, so it is possibly that the issue is only manifesting itself when FCPX is running.
Thought doubtful, just to rule out a few things:
– Does this happen with every project? If not, well that is crazy. Let me know.
– By any chance is this Red footage? If so it could point to a problem with your Red software or GPU.
– Have you reset preferences in FCPX by holding down command-option while clicking on the FCPX icon? If this fixes it, that again is crazy.
– Have you repaired disk permissions and repaired the startup disk? (Best to do in recovery, holding down command-R while restarting your Mac)If the above are ruled out I would try the following:
Create a fresh user admin account. Then launch FCPX in that account, if it persists, you at least ruled out the user account corruption issue.
If the new user account doesn’t resolve it, then try a reinstall of the OS. In recovery mode chose to install the OS and the installer will do a install without wiping out the user accounts.
If the OS recovery install doesn’t resolve it then this is pointing to a hardware failure.
Let me know if anything isn’t clear and how it goes.
——
T. Payton
OneCreative, Albuquerque -
Wow, thank you for the very detailed attention to this issue! I don’t think I’m going to have time this afternoon to try all these things but will get to it over the weekend. The footage for this is a range of things, H264, other quicktime formats, etc. Stuff that’s too slow in Avid AMA, my usual home.
-
Glad to help. Keep me updated.
——
T. Payton
OneCreative, Albuquerque -
I had a similar problem exporting from FCPX to Compressor.
Also coming from a programming background I had huge suspicions of what was causing this issue, so I reported the issue to the Apple team. To my surprise they emailed me back, first time ever after reporting an issue to them. They had me run a few tests, but also suspected I was right with my conclusions….
When you have an issue like this, where the system will run, then you perfom a procedure where things seem fine at first, but then everything begins slowing down, freezing, crashing, even if it happens relatively quickly…
This is the result of what they call a Memory Leak.
In essence that means that resources that are allocated to achieving a certain task aren’t getting freed, it is forgotten about in a sense, then the system asks for more resourses, and more again. This is a memory management issue, usually due to a programming error or oversight.
There’s nothing you can do about it until the code is fixed, but definately let Apple know. This is what they would call a critical issue and so it takes quite high priority. The only thing you can do is avoid what it is that set it off for you.
In my case it was in sharing from FCPX to Compressor, but it was Tiffen Film Stocks that was the culprit. Something is happening as it processes and it wasn’t freeing up the processes that it otherwise would have inside Final Cut.
-
So as it turns out, the problem isn’t FCPX-related — I was letting my bias against that program influence me. Instead it’s something that’s happening to me fairly randomly no matter what I’m doing, in a range of programs. It’s the same thing: a sudden freeze of the keyboard and trackpad, as well as any keyboard or mouse plugged into USB. Stuff in the finder menu appears to be still alive, like the battery/charger indicator, but I have no control over anything but the power button, so it’s a hard crash-out every time. I’ve reset PRAM and SMC several times, to no avail.
The computer is only about 6 months old, and pretty tricked out. The one shaky thing is that I’m using a somewhat old LCD as a third monitor, plugged with an adapter into one of the thunderbolt ports. I’m going to work for a while without that to see if it helps.
-
From what you describe It could be the OS or hardware, difficult to isolate. I would try the steps I outlined above, however you could bypass it and just clone your drive (your running a Time Machine right?) and then bring it to the Apple store, they will give it a shot to fix or just swap about the machine.
——
T. Payton
OneCreative, Albuquerque -
So all this….
I, too, am having this problem with this despicable program (I’m stuck for one project on Final Cut Pro X). Mid-2014 Retina macbook Pro, 16 gig ram, solid state drive. Just playing back a sequence, suddenly the keyboard and mouse do nothing. The sequence keeps playing, but I can’t stop it, crash out of FCP, or anything else. Only recourse is hard reboot. Never happened on any other software. I wish Cupertino would drop into a sinkhole”Was completely wrong( (as the OP came back later to admit), yet it still resides forever in the inter webs, ready to feed the next group determined to paint the program as “not ready for prime time.”
This crap happens to EVERY software.
One impatient knee jerk diatribe with scant evidence and an agenda – and another brick gets set in the wall of (Software A SUX!!!!!)
Odd, how essentially so few ever take the time to go back and remove or correct what they got totally wrong. (And, by the way, I’m just as guilty as anyone else if that.)
Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.
Reply to this Discussion! Login or Sign Up