Final Cut Pro and Spinning Beach Balls

I'm not sure if brettfromweatogue does, but I still do. I called the support and raised a case, and sent them screen capture. of FCP beachballing and crashing. If you can, I'd encourage you to do the same, otherwise they'll think it's just my individual case and they won't start working on a fix.

If you can report your issue using this please: https://www.apple.com/feedback/finalcutpro.html

Also it looks like it's a bug in MacOS as After Effects is affected too, something to do with the CPUs and MacOS.

After some investigating it actually looks like a Mac OS issue not a Final Cut Pro issue linked with the 10th gen CPUs so please can everyone also submit a form for Mac OS and report it as a bug report and explain your issue

Here is a sample that I wrote:

There is an issue with MAC OS and the new 10th gen CPUs when using applications such as after effects and Final Cut Pro. There is clearly a bug that is causing this issue. It looks like it's linked to the GPU on these new 10th gen processors potentially with with the G7 graphics. please fix this problem as I'm sure you're aware that many customers are returning these MacBook pro's with these new 10th gen processors because they cannot use it with these Pro apps. I am using Mac OS Catalina 10.15.5

Link is down below:

https://www.apple.com/feedback/macos.html

Aside from regularly checking this thread to see if Apple responded or someone found a workaround: is there anywhere else I can make my voice heard to notify Appel of this issue?

http://www.apple.com/feedback

You should probably mention this thread when you write.

Does it clear up or crash? For how long are the beach balls up? What are you doing when this happens? I recently finished a project and got a lot of them and would immediately just pull my hands away from the keyboard and mouse and wait it out. (The hand is quicker than the processor!) Was usually some long I/O operation. Usually they wouldn't last long, but sometimes it would just hang. After a minute or two and watching nothing happening except cpu accumulating in Act. Mon. I'd force-quit it. Memory pressure was always green.

Really need some more details here.

It usually happened for me when loading a project from disk. I just assumed it was doing the needed I/O and waited it out. I can't recall what other conditions it happened under, if any. I do recall once that using the eyedropper too many times would sometimes cause an instant crash. No beach ball, no error message -- the entire FCP window just suddenly goes bye-bye. I now do seem to recall that happened (the beach ball bit) at apparently random times and sometimes cleared up and sometimes just hung minute after minute, requiring a force quit. I think maybe it did just suddenly crash at other random times.

Oh, my setup:

Various versions of FCP 10.4

macOS 10.13.6 (High Sierra)

Please post the full Etrecheck report as Tom requested.

And just in case ut is not clear yet: what you are experiencing with beachballing on such short projects is NOT normal.

One other thing: are there any other resource hungry applications running at the same time?

Two things to try. Make a new admin user. Run FCP only. Import video from your iPhone into the library created on the new user. Run nothing else. Do you have the same problem?

The WindowServer was using a lot of CPU.

This "sugarsync" is crashing a lot. Is this trying to sync content to the cloud?

That may well explain the beachballs... as they are usually due to I/O operations.

I'd try uninstalling this, restarting your mac and see if things improve.

Exactly the same issue here with the same model. I called Apple Support and when I suggested that there is a problem with FCP/ 2020 MBPs compatibility, the guy said that he didn't get enough phone calls about it, so it must be my individual issue! Judging by so many people talking about this here and on YouTube - I don't think so!!

I'm not sure what to do, I've got 5 days to return it. I'm worried that it'll take them forever to release a fix. Or even worse, that it's a hardware issue.

I have a case open since the 15th about this problem, they have taken my machine and are sending me a new machine but I know this will still happen, I will keep everyone up to date but it'll be a few days at least before I get my new machine. Once it arrives I'll do my tests and report back here and to Apple, they still do not acknowledge that it might be a final cut pro issue.