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

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. 😟

Same issue as everyone else. Submitted feedback to apple:


FB7289548

Recent Similar Reports: None

Resolution: Open


Beta 9 couldn't come any sooner!!

FB7269056

I would not interpret the "Resolution:Potential fix identified - For a future OS update" feedback in some crash reports as confirmation that a fix will come in beta 9.

This is why you never run a beta OS on a machine you rely on. Also, posting on social media WILL NOT accelerate their timeframe for new betas. The whole point of the betas is to have patient users who submit feedback and wait for new builds to test yet again.


Use the Feedback Assistant and wait for updates to test, then submit feedback again to tell them if it is fixed or not. If you can't do this, you shouldn't be using the beta. It's the whole point of the beta program.

This is a beta OS...if you missed deadlines because you wanted the new toys before they were complete, then that's on you. They tell you not to install a BETA OS on a production device...it's NOT READY FOR RELEASE.


The finger pointing at Apple is foolish...you chose to install a unfinished operating system.


Stop complaining, file bug reports and wait for the next beta to TEST again.

Got the same issue too.


Process: Final Cut Pro [6963]

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

Identifier: com.apple.FinalCut

Version: 10.4.3 (324248)

Build Info: ProEditor-32424008011000000~2

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Final Cut Pro [6963]

User ID: 501



Date/Time: 2019-09-19 18:20:08.258 +0700

OS Version: Mac OS X 10.15 (19A558d)

Report Version: 12

Bridge OS Version: 3.0 (14Y905)

Anonymous UUID: D0427A3E-1122-5448-8267-612FF73BD430





Time Awake Since Boot: 2600 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

—Í çˇˇ

Same problem with iMovie. Glad I came here before uninstalling iMovie and deleting my Projects..

I’m sure Apple with release the fix once 10.15 is released. This is how Apple handles problems like this in the past.

ya ***!

Ross, this is arrogant, counterproductive stuff. We all want battled tested products. That requires real world testing. Your "walled garden" approach only reinforces developer process isolationism and keeps testing superficial while driving the daily users we all need to be using *and* breaking these mission critical apps to exit the beta program entirely. There is no real testing without real consequence, thus users can be rightfully frustrated to find a showstopper bug introduced into the 8th beta iteration with no rapid response articulated by developers. (and especially this late in release cycle, we're like 2 weeks out, c'mon) Clicking a few buttons isn't testing. Getting through an entire creative FCPX workflow with real deadlines, myriad media types, and zillion iterations of application personalizations *IS* testing. Responsiveness and foresight and obvious mitigation plans. That's all early adopters want. Treat people with the cold disdain of guinea pigs or lab mice and they'll dip out, talk crap and leave you with fragile software. No one wants that, Ross.