FCP 10.8.1 crash when using any Enhance Light / Color features

Question

Level 2

243 points

FCP 10.8.1 crash when using any Enhance Light / Color features

I've just tried to use the new Enhance Light / Color feature for the first time, and instantly when I click on the button to analyze and apply, FCP crashes. Note that it does the same when applying the enhancement via the Viewer's dropdown menu. I've tried with multiple clips in different libraries, and have reset preferences.

Briefly from the crash report:

Crashed Thread:        40

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process:   Final Cut Pro [98727]

Thread 0:
0   libsystem_kernel.dylib                 0x18bfc9db0 0x18bfc9000 + 3504
1   libdispatch.dylib                      0x18be592a8 0x18be54000 + 21160
2   VAML                                   0x1061127c4 loadCoreMLModel + 332
3   VAML                                   0x106112534 -[VAMLColorNeutralizerFactory modelForConfigurationID:error:] + 216
4   VAML                                   0x10611307c modelInstanceForConfigurationID + 68
5   VAML                                   0x1061141e0 -[VAMLColorNeutralizerProcessor initWithConfigurationID:error:] + 100
6   VAML                                   0x1061153e8 -[VAMLColorNeutralizerModelContainer initWithConfigurationID:error:] + 104
7   VAML                                   0x10611a824 -[VAMLColorNeutralizer initWithConfigurationID:error:] + 112
8   Filters                                0x1268d7108 -[PAEHDRColorCorrect neutralize_:] + 804
9   Filters                                0x1268d8350 -[PAEHDRColorCorrect neutralize:] + 44
10  AppKit                                 0x18fdd5a50 0x18fbfa000 + 1948240
11  LunaKit                                0x1054ca464 -[LKApplication sendAction:to:from:] + 108
12  Flexo                                  0x10c1c41e8 __36-[FFApplication sendAction:to:from:]_block_invoke + 60
13  Flexo                                  0x10c8cd56c FFApplicationHandleExceptionThatShouldNotBeIgnoredInBlock + 20
14  Flexo                                  0x10c1c416c -[FFApplication sendAction:to:from:] + 104
15  AppKit                                 0x18fdd5854 0x18fbfa000 + 1947732
16  AppKit                                 0x18fdd5798 0x18fbfa000 + 1947544
17  AppKit                                 0x18fdd56c0 0x18fbfa000 + 1947328

And the crashed thread in question (40) which shows that CoreML is clearly involved.

Thread 40 Crashed:
0   libsystem_kernel.dylib        
1   libsystem_c.dylib             
2   libsystem_c.dylib             
3   Metal                         
4   Metal                         
5   MetalPerformanceShadersGraph  
6   Espresso                      
7   Espresso                      
8   Espresso                      
9   Espresso                      
10  Espresso                      
11  Espresso                      
12  Espresso                      
13  Espresso                      
14  Espresso                      
15  Espresso                      
16  Espresso                      
17  Espresso                      
18  CoreML                        
19  libdispatch.dylib             
20  libdispatch.dylib             
21  CoreML                        
22  CoreML                        
23  CoreML                        
24  CoreML                        
25  libdispatch.dylib             
26  libdispatch.dylib             
27  CoreML                        
28  CoreML                        
29  CoreML                        
30  CoreML                        
31  CoreML                        
32  CoreML                        
33  CoreML                        
34  CoreML                        
35  CoreML                        
36  CoreML                        
37  CoreML                        
38  CoreML                        
39  libdispatch.dylib             
40  libdispatch.dylib             
41  CoreML                        
42  CoreML                        
43  CoreML                        
44  CoreML                        
45  CoreML                        
46  libdispatch.dylib             
47  libdispatch.dylib             
48  libdispatch.dylib             
49  libdispatch.dylib             
50  libdispatch.dylib             
51  libsystem_pthread.dylib       
52  libsystem_pthread.dylib

Running M1 Max 32 GB on Sequoia 15.0.1.

Any ideas how I can track down why engaging the machine learning features instantly causes a crash?

MacBook Pro 14″, macOS 15.0

Posted on Oct 14, 2024 9:30 AM

Reply

Answer 1

Top-ranking reply

Tom Wolsky

Level 10

151,971 points

Oct 14, 2024 1:38 PM in response to Derek Jones3

Do a complete uninstall of Chrome along with the keystone launch daemons. Reinstall FCP.

Two of your drives are full to being beyond useable. Remove at least 15% of the data from each drive and unmount them unless they're needed.

Reply

Answer 2

Oct 14, 2024 10:02 AM in response to Derek Jones3

Whenever the application crashes, you should delete its preferences, as they tend to become corrupted.

To delete preferences, hold down command and option while starting the application and click Delete Custom Settings. The application will start with default settings and open an "Untitled" library. Adjust the settings, reopen the library you were working, and see how it works now.

If the problem persists, there may be a software conflict. Please run Etrecheck and post its full report here. Use the "additional text" button and paste the report into the text box.

Reply

Answer 3

terryb

Level 4

2,620 points

Oct 14, 2024 6:57 PM in response to Derek Jones3

As Tom mentioned, Google's keystone daemons flood the video toolbox and have been known to actually break FCP. The solution after completely removing them (https://chromeisbad.com for instructions) is to reinstall FCP from the AppStore.

Reply

Answer 4

Derek Jones3 Author

Level 2

243 points

Oct 14, 2024 11:57 AM in response to Luis Sequeira1

As I mentioned in the original post, I've already tried launching after deleting preferences, no change. A new library and clip exhibits the same problem as well.

Thanks for the tip on Etrecheck. The kernel panic mentioned hasn't occurred since Sept after diagnosing a problem between my audio interface, a CalDigit USB dock, and my external display (would essentially kernel panic on wake from sleep) so that issue is resolved. The High CPU is a very intensive video processing app (Topaz Video AI) that's currently working on a large batch of files. The High CPU load for the last 18 or so hours is also expected. The FCP crashes are of course the ones mentioned here. Not sure of the other crashes except the "Hot" app which I installed to measure CPU temp when I first began using Topaz Video AI, and have since uninstalled.

Happy to hear any insight the report provides.

EtreCheck Report 2024-10-14

Reply

Answer 5

Derek Jones3 Author

Level 2

243 points

Oct 14, 2024 1:46 PM in response to Tom Wolsky

Hate Chrome, though I have one site I use pretty regularly, (Rev.com) that requires it. Will give it a go to see if that matters, though I don't see how it is related to this one specific feature of FCP.

Re: the drives, none of those full drives are used in conjunction with FCP, and the problem happens if I'm not connected to my dock at all, and am only using the system drive with no externals.

Reply

Answer 6

Tom Wolsky

Level 10

151,971 points

Oct 14, 2024 2:03 PM in response to Derek Jones3

Don't keep drives that full connected to the system. Every time the system looks them, it will freak out.

Keystone daemons run continuously and flood the video toolbox software.

Try Brave, which is Chromium based, instead of the Google browser.

Reply

Answer 7

Derek Jones3 Author

Level 2

243 points

Oct 14, 2024 4:23 PM in response to Tom Wolsky

Thank you for the helpful replies. While all of the other items were beneficial for my macOS health for sure, reinstalling FCP saved the day. Something must have gone wonky in the auto-update from the prior version. 🙌

Reply

Answer 8

dom_b1

Level 1

8 points

Oct 24, 2024 5:43 AM in response to Luis Sequeira1

This worked for me. I'd recommend trying this as it takes 2 seconds vs going through the headache of reinstalling Chrome (and logging back into all your sites etc) and reinstalling FCP (which takes time due to the file size). If it doesn't work, then fair enough, proceed with the other methods.

Reply

Answer 9

Tom Wolsky

Level 10

151,971 points

Oct 24, 2024 6:36 AM in response to dom_b1

Try Brave or Firefox instead.

Reply

Answer 10

Derek Jones3 Author

Level 2

243 points

Oct 24, 2024 7:56 AM in response to Tom Wolsky

Yes, don't reinstall Chrome! :P

Reply