Final Cut Pro X is crashed

I just upgraded to beta 8 and FCPX is crashed whenever I open the app. I tested with empty library but it's same. Reinstalling the app isn't work. Here is the head of crash log. Anybody had same issue?


```

Process: Final Cut Pro [856]

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

Identifier: com.apple.FinalCut

Version: 10.4.6 (342230)

Build Info: ProEditor-34223000026000000~1

App Item ID: 424389933

App External ID: 830604740

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Final Cut Pro [856]

User ID: 501



Date/Time: 2019-09-10 23:54:02.254 -0700

OS Version: Mac OS X 10.15 (19A558d)

Report Version: 12

Bridge OS Version: 4.0 (17P50553c)

Anonymous UUID: F51328D8-177B-E31D-09AA-85094C0CFB4E



Sleep/Wake UUID: C3595477-D6FA-414D-A052-5DCCF7E324DE



Time Awake Since Boot: 810 seconds

Time Since Wake: 590 seconds



System Integrity Protection: enabled



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



Exception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY



Termination Reason: LIBSYSTEM, [0x2]



ID Vend/Dev

9d9e 687f1002

Seconds Ago ID Type

1300.0 9d9e Attach



Application Specific Information:

assertion failure: "((void *)0) == tsd->NSCurrentOpenGLContext" -> %lld

—˙ÿíˇˇ

```

Accepted Reply

Its Monday, beta 9 out... just like I thought!! Hope it fixes FCPX, still downloading...

Update working for me.

Replies

Ross isn't suggesting a "walled garden" approach. He's talking about not relying on beta software for production uses.


By all means, load real projects into real applications on a beta system to test it. If and when that fails, report it to Apple, and then go back to your system that's running non-beta software and get your work done.


But by no means should you be installing beta software on a production machine, with no other way to get work done, and then complain to Apple about how their product isn't living up to your expectations. If you don't have a secondary system to get production work done, you shouldn't be installing beta software, unless you're ready to deal with situations exactly like this.


Tim

I have the same problem. Is there a solution yet?

😟 Here's another - FB7287161


LET'S get this fixed dudes. I feel new betas were coming every few days and now suddenly we waitttttt... shrug...

This is an obtuse and dated view of software adoption. Who are all of these users with both time and non-primary computing resources to do unpaid end-to-end testing without easy and obvious roll back functionality? This is just another defense of contrived testing protocols. Every time one of you guys ***** out a tired defense of an unresponsive development institution, it resets the expection that "they give it and we take it." Why do you want it this way? Re-read Ross' response. There's absolutely no empathy there. No solution-ing. Just crass smugness.

Do you think Apple will ditch FCPX like it did with Aperture?


Guys. ***** FCPX, Download Davinci Resolve 16. It's free and has better stuff. Colour grading is much simpler.


It's a disgrace that it's a week on and no sign of an update on the Beta OS or and Update for the App it's self.

Lets hope they push an update by Monday. This beta was old as soon as FCPX started crashing on me... but thats the breaks with betas.

YUP! Same issues , Called support they said " Wait for the Catalina update later this month." :-(

APPLE! FCP folks , WE have work to get out ... We NEED THIS FIX & FAST. Thanks!





https://media.giphy.com/media/jUKldPpZHZClbMwA7R/giphy.gif

I have the exact same problem! Does anybody have news on this?

Yep. Same here. I heard by the end of the month there would be a fix, but cant confirm that.

Thanks for sticking up guys.

People like Ross Kinard are either trolls or workl for Apple or both.

Apple has been rolling out substandard crap for years now as i was warned by former Apple users.

To use 7 beta versions with the software working fine and then to have the patest one cause crashes is ridiculous; furthmore to not have an easy way to roll back (as stated) is beyond ridiculous.

AND FURTHORMORE to be almost two weeks after the latest beta version, At LEAST 50 bug reports sent and STILL with ZERO ANSWERS, from Apple, the so-called "pro" team - except to say that they know nothing about beta versions is DISGUSTINGLY REPREHENSIBLE.

Period.


Apple's days are numbered.


The numbers are dropping and if you do a search, you'll see that this latest OS *****.


Gnite.

Final cut pro Ver 10.4.6 crashes with Catalina 10.15 OS, When will there be a fix?

Same Issue and it's been like this for like 10 days.. Strange how apple didn't know about it! FCPX is one of the main reasons to get a MacBookPro..





Process: Final Cut Pro [1220]

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

Identifier: com.apple.FinalCut

Version: 10.4.6 (342230)

Build Info: ProEditor-34223000026000000~1

App Item ID: 424389933

App External ID: 830604740

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Final Cut Pro [1220]

User ID: 501



Date/Time: 2019-09-23 08:23:13.840 +0300

OS Version: Mac OS X 10.15 (19A558d)

Report Version: 12

Bridge OS Version: 4.0 (17P50553c)

Anonymous UUID: 0E75CC76-B284-0E96-9B69-D27DECBFCBEF





Time Awake Since Boot: 800 seconds



System Integrity Protection: enabled



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



Exception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY



Termination Reason: LIBSYSTEM, [0x2]



Application Specific Information:

assertion failure: "((void *)0) == tsd->NSCurrentOpenGLContext" -> %lld

— ∫èˇˇ

Beta 9 is out. Please let me know if the issue is resolved.

Thanks man. I've just downgraded my MacBook Pro to MacOS Mojave. But I'll install the Beta 9 and see if FCPX is working again. 🇧-1F1F7;👍-1F3FC;