FCPX continuous crashing

it crash again... reopenFCPX relaunch the "copy project to" and another warning: "Optimized and proxy media do not exist for some clips. To generate optimized and ProRes proxy media, click Transcode. Transcoded media will be created in the folder “FCPX Library”.

Sorry Ronny, but the issue isn't solved... I really don't know how's happened. Never had a problem with FCPX before...

No worries, we don't give up easily (-:  It does look like it's more complicated than expected.

Don't try copying the Project again, that probably wont't work. Instead, we will try to find what there is in the project that crashes FCP. Does it crash completely, or does it just hang (beachball) and you need to force-quit?

it completely crash, I click (one click) to select the project and the beachball start to roll.. after maximum 10 second it crash

Okay, and do you get a message when it crashes, like a crash report? If so, we would need to see that report to find out what exactly caused the crash.

no message, FCPX only disappeared

No problem, we will try to find the crash report. This is from memory:

in Finder, select ‘Go’ while pressing the Option key.

In the Go menu you will see ‘Library’. Double-click Library to open that folder.

Inside the Library folder you will see a ‘Logs’ folder, open it and inside the Logs folder open the ‘DiagnosticReports’ folder.

In the DiagnosticReports folder you should see some crash reports. Select the most recent one, drag it to your desktop and post it here.

I've got 3 with the same date.. Load all

One would be enough, but yes post it here so we can have a look.

- Ronny

Minguzzi wrote: I've got 3 with the same date.. Load all

Please post it as an attached .txt file, not in-line. The new forum software makes examining large in-line posts difficult.

so... it's ok this way???

sorry, maybe was wrong... Re-post

sorry, I'm new in this forum... what I have to do to post offline?

Send the crash report to me, I will post it on the forum:

ronnycourtens@mac.com

- Ronny

ok

Update: I had asked OP to send us the crash logs but strangely enough he does not find any crash logs on his Mac, except an old one from 2018. We have tried Library > Logs and Finder > Search ".crash". When I do any of these on my Macs, I always get a list of crash logs for all applications.

I cannot believe there are no crash logs on that Mac and I'm on the road now. Does anyone know if there are any other places where to find Final Cut Pro crash reports?

Thanks!

- Ronny

Have you tried XML export/import?

ronny courtens wrote: ...he does not find any crash logs on his Mac, except an old one from 2018...I cannot believe there are no crash logs on that Mac and I'm on the road now. Does anyone know if there are any other places where to find Final Cut Pro crash reports?...

Ronnie, maybe he looked in the system-level /Library tree, not the user-level ~/Library tree. However doing OPT+Go in Finder and picking Library should have taken him to the right place.

He can also run the Console app and pick "Crash Reports" in the left sidebar, which should show any app-specific crash logs. If present, he can right-click and pick "Reveal in Finder" to get the file, then upload that. To run console do CMD+spacebar and enter "console", then return, or run it from /Applications/Utilities.

He can drop any files here and I will post them: www.transferbigfiles.com/dropbox/joema

There are a few cases where an app will shut down without a crash log. E.g. if the system is out of memory or has some other problem.

To inspect this I recommend he (1) Verify he has at least 20% free space on all drives, and (2) Activity Monitor>Memory tab shows no memory pressure, e.g, a green graph, not yellow or red.

If nothing abnormal seen there, I recommend he reproduce the problem, then grab the system log and upload to the above link. Note the system log is normally full of assertions and warnings, even on a properly-running system, so don't panic over those. The trick is examine the system log for clues surrounding the time of the event. The system log is on the left sidebar of the Console app, right-click that to Reveal in Finder, or else in Finder do Go>Go to Folder, and enter /private/var/log, then grab the system.log file and upload it.

I recommend he also check for any 3rd-party kernel extensions, using the following terminal command:

kextstat | grep -v com.apple

It's also possible he's had kernel panics. These can be examined with the following terminal command. Enter exactly as shown, then wait about a minute, then do CTRL+C to cancel and show results.

log show --predicate 'eventMessage contains "panic"' --last 7d

He can copy/paste the terminal results to TextEdit, save as a .txt file and upload.

A common cause of FCP crashing is out-of-date or buggy plugins. If we could obtain an FCP crash log that might help isolate those. He mentioned running Magic Bullet, so he could try uninstalling that using the Red Giant Application Manager (which should be in /Applications. If not he could possibly download it from here:

www.redgiant.com/application-manager/

Normally FCP data integrity is excellent but if the library gets damaged it can cause unexpected crashes. As Andreas mentioned, exporting a full library XML then loading that to a new test library might be good to try. Sometimes that filters out internal library damage.

Hi Minguzzi
Sorry to hear about your issues.
Just a couple of other things to try… (You have some great expert help here)

Shutdown your Mac- A full shutdown purges many temp files and may reset the database, might help, won't hurt. I always cycle a full shutdown when having issues, same for FCP preferences (Option+Command on launching FCP)

Launch FCP in a new user account. - It is possible that your User account is messed up. Can you edit in different user account? 

Run EtreCheck - EtreCheck may find issue. I suspect a corrupt or out of date plug-in(??)
Update or remove the plug-in.

As to the logs… I think Joema is right,  OP most likely looking @ system library not user logs. 

If you do not see a splash screen immediately after a crash, then you have "Share Mac Analytics" turned on in System Preferences>Security and Privacy. If you unselect this, you will get notified of crash with "Ignore" or "Report" splash screen. Clicking on "report" will display a copy of the report for examination and you can then copy it or click to "Send to Apple". This is the report we need to see so copy it and create text file. This is in reverse chronological order and the thread that crashed will be noted and near top of report.

As to the use of Console, you need to know the time of the crash. Make it crash and immediately note time, then you can isolate the logs to a small time window. Joema-7days, Yipes!;P sleep inducing, but OP hasn't said Mac did an actual Kernel Panic, just FCP app crash. I'm not big fan of unified logs

XML export/import may clear up issue.

Reinstall FCP.

Hope you work it out, best of luck,
Greg

An update. The Red Giant plugin was causing the issue. Completely removing it using the uninstaller, then restarting the Mac and launching FCP with fresh preferences has brought the projects back to life. Thank you to everyone who has helped with suggestions. Much appreciated.

- Ronny