16" M1 Max MBP - Memory Leak after opening FCPX

Update

I wanted to provide a quick update to my original issue to say that I've been able to narrow it down to a specific Project (unfortunately one I need to still edit!).

This morning I worked in a separate library for hours and memory was normal while I edited, exported etc. Switching gears back into the "problem" library I seem to be able to reproduce the issue immediately whenever I went to export the project.

It seems to get to around 21% of the export and then memory skyrockets and makes me force quit every time. I attempted to move this project OUT of this problem library and into a new library/event but the problem persists leading me to believe its THIS project. Looking at the edit (especially around the 21% mark - there are no external plugins that I could find on any of the clips. The sequence is about 15 logos "scaling" in - text fading in and a ken burns masked photo effect behind it all. What's weird is I did this same project - almost exact same edit with 8 logos instead of 15 early in the week and everything was smooth sailing. I have deleted the render files in case someone asks. (screenshot attached)

I even tried sending to to Compressor for export - to get it out of FCP and memory shot up there as well. While it didn't crash the app it did fail the export with an error message:

Failed: Error: RequestCVPixelBufferForFrame returned: 3 for absolute frame: 460

Since it is not impacting every Final Cut project I'm assuming there is something super funky about this one but with clear render files and no specialty plugins I'm still kinda lost as to what it is I'm looking for or how to narrow it down further.

I hear you all on the Chrome and Color Finale and am actively working to remove but something tells me this is project specific. What should I check?

Thanks @Tom

I can now mark this as solved! I noticed at frame 460 it was the first frame of one of the 15 logos I used. As soon as I deleted and replaced that file with a new one it worked flawlessly. Its amazing to me that 1 single .png can lead to a complete app crashing memory leak but it did.

On that note - is there anyone at Apple on the Final Cut team I should send this file to as a potential fix for future updates? Im sure there are always going to be bad files, but I wonder if the team can fix whatever issue this one caused or even consider adding in a "bad or corrupt media" message for one like this.

Yes, however in this case the share didn't fail, it froze and app crashed due to the memory leak.