fcpx crashes no matter what

HELP. I have read every forum looking for an answer but nothing is working. Final cut just refuses to work for me. Every action creates a beachball and eventually eats up enough memory to crash the program. I have a 2015 pro, with the latest version of Big Sur and a clean copy of final cut. I've deleted my preferences, deleted render files, started all over with a new project, ran etrecheck, made plenty of space on both my computer's hd and my external hd (where my media and libraries are located) and so much more - nothing is fixing the problem. Project is past due. My next step is to throw my laptop out the window. Help me fam, you're my only hope.EDIT: I have also uninstalled Chrome and all of its components. No plug-ins on the project, just one compound clip consisting of 16 stacked videos and a couple of transitions.

fcpxwillbethedeathofme wrote: ...Final cut just refuses to work for me. Every action creates a beachball and eventually eats up enough memory to crash the program. I have a 2015 pro, with the latest version of Big Sur and a clean copy of final cut...

If FCP memory consumption continuously increases then the app crashes, that is most commonly caused by a buggy plugin. Evaluate all plugins being used and update them. CoreMelt plugins can be updated here:  coremelt.com/pages/downloads

If you have any plugins from FxFactory, update the FxFactory app and then update those plugins.

If you have plugins by Pixel Film Studios, those have caused lots of problems. Try to update those or maybe even de-install them and use a replacement.

Try to make a snapshot duplicate of the project, open that, select all clips with CMD+A, then delete all Fx using Edit>Remove Effects. Try editing that timeline with no Fx and see how it behaves. If it works OK, that further implies an issue with some effect. However the code for some effects can still adversely impact FCP even if not used in the current project. However this is an easy test to perform, so go ahead and try it.

In case there is some corruption in the project database, export the project XML, close the old library, create a new library, then load that project XML in that new library. That can help isolate if its a project database issue.

If it still crashes, please save the full crash log to a .txt file and post it here as an *attachment*, not in line. 

If the entire machine ever crashes or hangs, that implies a system-layer issue, not FCP.