Final Cut Pro X is crashed

Same issue here. I have reached out everywhere I know to reach out and all I get is crickets, (apparently I reached out too much as I got a nice note from Apple telling me to stop reaching out on public forums), my bad.

It amazes me that FCP folks didnt see this coming or know anbout it and get ahead of it.

I have cleared preferences, reinstalled and still nothing. I really need FCP X to open and function.

If anybody figures out a resolve I would sure love a heads up.

Thanks in advance -

Chris

Ohhh thank god it's not just me then.. So we are all having same problem.. Hope it gets a fix real soon!

I think I will no longer use the beta version of the system.

H!

Have you figured something out with your own app?

I am experiencing the same crash, assertion failure: "((void *)0) == tsd->NSCurrentOpenGLContext" -> %lld, in my own app on macOS Catalina 10.15 beta 8 (build 19A558d).

My application uses VLCKit, which in turn relies upon OpenGL, to stream IP cameras; what is interesting, is that it does not crash when I launch and leave it be, but it crashes as soon as I switch to a different URL (which causes the current playback session to be terminated and a new one to be started).

I tried performing the same operation using the latest VLC application (File > Open Network) and the result is the same: it works the first time, crashes immediately with the next URL.

What is worst, my own app attached to the Xcode debugger does not point to a specific part of my code, it just logs "Message from debugger: Terminated due to signal 9".

I am very worried that Apple might have killed OpenGL sooner that expected, so any suggestions is very much appreciated.

Thanks!

After a bunch of attempts, FCPX still didn't work in beta 8, so I had to re-assemble a short project I was working on in the latest build of Premiere Pro (clean install of version 13.1.4 build 2) and it ran quite smoothly. Fortunately, I worked from a bunch of already rendered clips so it wasn't too much of a hassle. After Effects also works fine (an older version already on my MacbookPro, 16.0.0 - build 235).

Same issue here

iit's safe to say that this is a major blocker bug...

I havent got any updates and when I contacted the "Pro Team" they didnt know anything about this.

I installed the previous beta from last week and everything worked until... all of a sudden it didnt. FCPX started doing the same thing again so I figured maybe that was because a patch was downloaded to fix the latest update (which is now screwing up the old one) so I updated to the latest CVatalina and it's crashing. Incidentally, it's worse than ever because it literally flashes on the screen and doesn't open for even a second.

I've uninstalled FCPX and mInstaller and I'm going to reinstall them - which might do something.

I swtiched to Mac this year and I'm having a lot of disappointment, especially in the lack of support. Nobody knows anything and i have yet to have someone say, "yup, we've had calls about that problem all day, here's how to fix it!"

Instead, it's nobody knowing anything about anything. In 9 months, I know more about the OS then people I've called to help me.

MacBook 2019 - the 6k one so it ain't the hardware.

APPLE - as an idea and what it promises is really cool; it's just nowhere near what it should be.

I hope that with all of the new OSs and being that i came into the Apple family at this transitioning time; i hope that all the kinks get worked out in the next month.

With this problem and others, I have missed deadlines - and I am NOT being dramatic either...

...okay, a little dramatic.

Get it together, Apple!!

Chris

- the complaining dude with the iPhone 11 already on his mind.

PS - I'll update everyone on my reinstall.

Have same issue with Final Cut Pro and Motion on the newest developer beta. I have sent a bug report with the crash log and suggest everyone here does the same.

I don't think that this Bug is related to the fact that the future Development of OpenGL is depreached.

Apple currently has with Garageband, FCPX ... many Applications on the Run which are using OpenGL-Functions for rendering and has already not moved them forward to use Metal. It makes no sense that Apple make OpenGL not working if in the same time Applications from Apple themselve are published which are not usable in Catalina and there are no alternatives.

I hope the developers can fix this issue before GM eventually in the next beta.

This error >>assertion failure: "((void *)0) == tsd->NSCurrentOpenGLContext"<< occurs in

Final Cut Pro X (as seen above)

iMovie

Garageband

VLC, Enpass (QT-Related)

I think there are a lot more Applications with this issue. I hope this will fixed with the next Beta.

Using Feedback Assistant, I've just filed radar FB7276584, with attached crash reports and a sample project that reliably crashes on Catalina beta 8, but is stable with previous versions.

I just submitted the issue through the feedback assistant: https://feedbackassistant.apple.com/

to my surprise I get a notification saying:

Recent Similar Reports: None

Resolution: Open

How about sending the issue, the more of you that send it the more likely it is to be resolved.

🙂

That would be very useful.

It also helps to specify in the radar bug report that there ore others reports already submitted for the same issue: mine was FB7276584 and I'm also aware of FB7281945.

And yet another. Pro Video will not update either, and now I discover that iMovie suffers from the same problem, so even a simple job can't be done. I don't have a computer in the house that I can go back to Mojave on. Apple customers ask us to help, we try and get this kind of a problem. Oh well, can't say we were not warned. Hopefully in October good things will happen, if not before. I feel sorry for those that depend on this for a living.

My report is FB7283002, I am lucky that I have another Mac I can work on but it is older and slower than my 5K iMac.

My report is FB7253859, I am now back to using mac mini 2012 vintage, 16Gb plus fusion drive until this is fixed!

I was able to roll back to Mojave, using the internet recovery system.

My report is FB7265136.

When I went back and looked it also said, "Similar Reports: None"

That's a little frustrating.

For those keeping score, current report #'s for your convenience are:

FB7253859

FB7283002

FB7265136

FB7281945

FB7276584

55341498

Did anyone happen to have luck running the supplemental update and the Pro Video Formats 2.1 updates that were released today? If I ran them seperate, the Supplemental update ran and installed, but the Pro Video Formats 2.1 got stuck and aborted.

Just thought I would check and see if any body had any luck with those.

- Chris

Do you have new about the new releasedof Beta 9 ? It's urgent ! I made a mistake to testing catalina during an editing ! Now i have an urgence for it.

Same problem here! I’ve been posting on social media like cray for them to fix them. I really don’t want to downgrade but have a video use this weekend And might have to borrow a friends computer to just get work done. iMovie doesn’t open up either :(

My report is: FB7284848

Starting to see some similar reports getting logged. If everyone submits Apple will put more importance on it.

Recent Similar Reports: More than 10

Resolution: Open

I updated them and have no change. 😟