fbpx
3 Post Moderation Rule for New Boarders (25 Jan 2021)

New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.

HELP - FCPX Crash on a large project

More
12 Oct 2022 13:34 - 13 Oct 2022 09:11 #122440 by ElricDesDragons
Hi !

First of all many thanks for your awesome job and help provided.

I'm running a large professional project that since yesterday is consistently crashing.
I have red other topics about the subject ant I have disabled all my plugins, restarted, deleted rendered files, ... With no success or resolution of the problem.

I'm running FCPX on a M1 MacBook Pro 64Gb 2To disk. Library is on internal SSD disk.
Everything is up to date, and no pirated softwares installed.

Here is the crash log sent to apple in attachement.

File Attachment:

File Name: FCPXCrashlog.rtf
File Size:3,449 KB


I'm totally incapable of reading it... So if someone can provide any help, I'll be very grateful !

Many thx for your help !
Waiting for any advice I'm going to try to export it on xml and import it into a new library as already provided as a solution in an another topic.
Attachments:
Last edit: 13 Oct 2022 09:11 by ElricDesDragons.

Please Log in to join the conversation.

More
13 Oct 2022 14:06 - 13 Oct 2022 14:07 #122454 by joema
This one is technically a hang not a crash, although the end result is the same.

It appears an FCP thread became stuck waiting on another FCP thread to release a write lock. It's possible that thread encountered a "handled exception", which means a violation that would normally have crashed the process but it was handled by an exception routine. When this happens, sometimes the exception handler does not cleanly release all assets held by the faulting thread and the other threads back up on some asset.

In computer science there is an viewpoint called "fail fast" which argues that structured exception handling should not be used, rather the process should be allowed to just crash. They argue that the debug info from an immediate crash is higher quality since trying to handle the exception often degrades the process and when it finally hangs or has an unhandled exception you can't deduce the original cause. I don't know the current academic position on that but it was formerly a hot topic.

It appears the first thread might have been part of background rendering. If you are using background rendering, try turning that off in FCP preferences. Often the M1 Max is fast enough that you don't need a rendered timeline. If you need to render certain clips or the entire timeline, you can do that by selecting the clips or the entire timeline with CMD+A, then render it with CTRL+R. When the render dots above the timeline go away it is rendered to cache.

It should not crash due to background rendering; this is just a possible workaround.

You are also using FxFactory 8.0.3. That is the latest version and it normally works OK, but you might try completely removing it. This is even if you aren't using any FxFactory effects in the current timeline -- remove the app itself, reboot then see if it made any difference.

If some other process has the library opened while FCP is running it could cause a hang or crash. E.g, if Finder, a utility, a NAS copy or external backup has the library open it can cause problems. Consider if that might be a factor in your case.
Last edit: 13 Oct 2022 14:07 by joema.

Please Log in to join the conversation.

More
13 Oct 2022 17:12 #122455 by ElricDesDragons
Hey !

You have literally saved my day.
Auto Rendering was part of the problem and deactivating it stopped the freezing and crashing.

Many thanks for your help on that one !
I hope it will not come back for the final rendering of the project... 

I'm not using any FxFactory plugin for this project and have deactivated all of them.
I'll try later to uninstall the host plugin itself instead of just keep it "in sleep mode".

Many thanks again for the accuracy of your analysis and workaround !

Please Log in to join the conversation.