MTLCompilerService quit unexpectedly

Report · Nov 07, 2016

System Specs

MacBook Pro 2012

16GB RAM

NVidia GeForce GT650M / 1Gb VRAM

960GB SSD/432GB Free

6TB WD MyBookDuo USB 3.0 External Drive

MacOS Sierra 10.12.1

Adobe Creative Cloud v3.9.1.335

All Apps updated to 2017 versions approx. 8 days ago (Premiere, Media Encoder, After Effects.)

I also maintain a copy of Encore to author the periodic DVD

Within the last week or so, I keep getting a "MTLCompilerService quit unexpectedly" whenever I start any of the Adobe Applications that I regularly use (Premiere, Media Encoder, After Effects ). Photoshop, and Audition seem to start ok without this error. This began with the recent update to Adobe Creative Cloud.

Crash Report is below. Any help or insight into this issue would be appreciated.

Thread 4 Crashed:

0 com.apple.GeForceAIRPlugin 0x00007fff8db0301a NV::AIR::LoadViaTextureHelpers::emitBufferTextureLoad(llvm::Module&, llvm::IRBuilder<true, llvm::ConstantFolder, llvm::IRBuilderDefaultInserter<true> >&, llvm::Value*, llvm::Value*, llvm::Type*) + 1284

1 com.apple.GeForceAIRPlugin 0x00007fff8db03c20 0x7fff8db00000 + 15392

2 libLLVMContainer.dylib 0x00007fff9fda7e25 llvm::legacy::PassManagerImpl::run(llvm::Module&) + 917

3 com.apple.GeForceAIRPlugin 0x00007fff8db49a35 NV::AIR::CompilationRequest::Compile(NV::AIR::CompileParams const*, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >&) + 627

4 com.apple.GeForceAIRPlugin 0x00007fff8db5d4d2 MTLCompilerBuildRequest + 2478

5 com.apple.MTLCompiler 0x00000001079b9b2a MTLCompilerObject::buildRequest(unsigned int, unsigned int, void const*, unsigned long, void (unsigned int, void const*, unsigned long, char const*) block_pointer) + 7412

6 com.apple.MTLCompilerService 0x000000010782b133 compileRequestMain + 211

7 com.apple.MTLCompilerService 0x000000010782b74e ___ZL29MTLCompilerServiceHandleEventPU24objcproto13OS_xpc_object8NSObject_block_invoke + 791

8 libxpc.dylib 0x00007fffa7db8f82 _xpc_connection_call_event_handler + 35

9 libxpc.dylib 0x00007fffa7db794b _xpc_connection_mach_event + 1707

10 libdispatch.dylib 0x00007fffa7b29f36 _dispatch_client_callout4 + 9

11 libdispatch.dylib 0x00007fffa7b2a371 _dispatch_mach_msg_invoke + 414

12 libdispatch.dylib 0x00007fffa7b3a9d2 _dispatch_queue_serial_drain + 443

13 libdispatch.dylib 0x00007fffa7b28cab _dispatch_mach_invoke + 868

14 libdispatch.dylib 0x00007fffa7b3a9d2 _dispatch_queue_serial_drain + 443

15 libdispatch.dylib 0x00007fffa7b2cd41 _dispatch_queue_invoke + 1046

16 libdispatch.dylib 0x00007fffa7b3b3bf _dispatch_root_queue_drain_deferred_item + 284

17 libdispatch.dylib 0x00007fffa7b3e1b0 _dispatch_kevent_worker_thread + 978

18 libsystem_pthread.dylib 0x00007fffa7d7160f _pthread_wqthread + 1004

19 libsystem_pthread.dylib 0x00007fffa7d71211 start_wqthread + 13

Report · Nov 07, 2016

Moving to Premiere Pro

Report · Nov 11, 2016

Just as an update, it seems in my uneducated opinion that this has something to do with the NVIDIA driver that is packaged with MacOS Sierra. I updated to the NVIDIA beta web driver on the nvidia website, and the issue seems to have gone away. Here is the driver I used...

NVIDIA DRIVERS Quadro & GeForce macOS Driver Release 367.15.10.15

Unfortunately, this is a beta driver, so I am not sure what problems I have traded for. Only time will tell...I will update after a week of running the web driver. Warning - update your graphics driver at your own risk, and please research the rollback procedure just in case things go bad.

Report · Nov 14, 2016

Exactly same laptop and same problem. Waiting for your update about how this driver works.

Thank you.

Report · Nov 15, 2016

So far so good - no Kernel Panics and Mac seems stable. The MTLCompilerService error has not yet returned since switching to this driver.

On a different note, CUDA seems to be sporadic in premiere & media encode with this driver. I use OpenCL anyway, when I used CUDA immediately gives an error (unable to create frame). (The Native driver did not have this problem) I rendered two small projects using OpenCL and they rendered out OK. One other project rendered out OK using CUDA, so the results do not seem consistent on the rendering front.

YMMV.

Report · Nov 27, 2016

mmm… After two weeks with the beta driver I have experienced around three to four kernel panics. Bizarrely the kernel panics happened using Safari.

I went back to the OS X default graphics driver. Waiting for a more stable version.

Report · Nov 19, 2016

Same error every time I start After Effects. MacBookPro10,1. Doesn't seem to be causing any practical problems or keeping me from doing anything.

Report · Nov 27, 2016

I did not experience any kernel panics within premiere, but another application that I use (propesenter) Became very unstable this weekend using the web driver. Switching back to the OSX native for now - as a previous poster mentioned, these errors (while annoying) seem to be cosmetic. Hopefully Adobe will release a fix.

Report · Dec 14, 2016

It seems that 10.12.2 has solved this annoyance.

Report · Dec 16, 2016

Same here. Not only was I getting the MTL Compiler Service warning when I opened AE (or Premiere), but I kept getting a Divide by Zero error (17::17) when I tried to Preview or Render a simple image sequence. Other problems included not remembering my frame interpolation and misshapen Time Remapping graphs.

The update came through this morning and now things are working. I'm SO relieved! The project I'm working on is a holiday animation, and I was really starting to panic.

Report · Oct 24, 2017

Hi Andre,

According to Premiere Pro engineering, updating to MacOS High Sierra solves this issue.

Thanks,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

Report · Oct 26, 2017

I am having the same issue - "MTLCompilerService quit unexpectedly" everytime I open Premiere Pro CC 2018. I updated the OSX to 10.12.6. Still getting the error when opening Premiere. I switched to the OSX Default Graphics driver - no error message when opening Premiere, but then lost my second monitor and nothing looks or playsback correctly.

So the PP engineering department is wrong in my case - updating to High Sierra has not solved this issue.

Mac OS Sierra

Version 10.12.6

Mac Pro (Mid 2010)

Processor 2 x 2.4 Ghz Quad-Core Intel Xeon

Memory 52 GB 1066 MHz DDR3

Graphics NVIDIA GeForce GTX 1080 8192 MB

Nvidia driver: 378.05.05.25f01 (up to date)

Thread 4 Crashed:

0 com.nvidia.web.GeForceAIRPluginWeb 0x0000000107bf1893 0x107739000 + 4950163

1 com.nvidia.web.GeForceAIRPluginWeb 0x0000000107bf1ac7 0x107739000 + 4950727

2 com.nvidia.web.GeForceAIRPluginWeb 0x0000000107bf29ed 0x107739000 + 4954605

3 com.nvidia.web.GeForceAIRPluginWeb 0x0000000107bf3beb 0x107739000 + 4959211

4 com.nvidia.web.GeForceAIRPluginWeb 0x000000010776114d 0x107739000 + 164173

5 com.nvidia.web.GeForceAIRPluginWeb 0x00000001077612e2 0x107739000 + 164578

6 com.nvidia.web.GeForceAIRPluginWeb 0x00000001077590bd 0x107739000 + 131261

7 com.nvidia.web.GeForceAIRPluginWeb 0x0000000107758284 0x107739000 + 127620

8 com.nvidia.web.GeForceAIRPluginWeb 0x000000010776970f 0x107739000 + 198415

9 com.nvidia.web.GeForceAIRPluginWeb 0x000000010778a455 0x107739000 + 332885

10 com.nvidia.web.GeForceAIRPluginWeb 0x0000000107789c03 0x107739000 + 330755

11 com.nvidia.web.GeForceAIRPluginWeb 0x000000010779c252 MTLCompilerBuildRequest + 1170

12 com.apple.MTLCompiler 0x00000001076ac9d6 MTLCompilerObject::buildRequest(unsigned int, unsigned int, void const*, unsigned long, void (unsigned int, void const*, unsigned long, char const*) block_pointer) + 8344

13 com.apple.MTLCompilerService 0x000000010751df03 compileRequestMain + 211

14 com.apple.MTLCompilerService 0x000000010751e506 ___ZL29MTLCompilerServiceHandleEventPU24objcproto13OS_xpc_object8NSObject_block_invoke + 847

15 libxpc.dylib 0x00007fffbddcef96 _xpc_connection_call_event_handler + 35

16 libxpc.dylib 0x00007fffbddcd957 _xpc_connection_mach_event + 1707

17 libdispatch.dylib 0x00007fffbdb4b726 _dispatch_client_callout4 + 9

18 libdispatch.dylib 0x00007fffbdb4b999 _dispatch_mach_msg_invoke + 414

19 libdispatch.dylib 0x00007fffbdb5b7db _dispatch_queue_serial_drain + 443

20 libdispatch.dylib 0x00007fffbdb4a497 _dispatch_mach_invoke + 868

21 libdispatch.dylib 0x00007fffbdb5b7db _dispatch_queue_serial_drain + 443

22 libdispatch.dylib 0x00007fffbdb4e306 _dispatch_queue_invoke + 1046

23 libdispatch.dylib 0x00007fffbdb5c24c _dispatch_root_queue_drain_deferred_item + 284

24 libdispatch.dylib 0x00007fffbdb5f27a _dispatch_kevent_worker_thread + 929

25 libsystem_pthread.dylib 0x00007fffbdd9447b _pthread_wqthread + 1004

26 libsystem_pthread.dylib

Report · Oct 31, 2017

same for me, this started when I upgraded to CC2018(version 12.0.0) and I was already on Mac OS 10.12.6. the error is annoying but not preventing me from working. error repeats on startup but not while working.

Report · Nov 21, 2017

Not everybody can upgrade to High Sierra anyway. I hope Adobe addresses this problem!

BTW - I'm on an older MacPro tower, with an upgraded (non-Apple) graphics card flashed for the Mac. Error does come up when starting - comes up multiple times, but doesn't seem to affect performance on Premiere or AE for me, after the initial annoyances. I suggest we ALL let the crash reporter report each time - so Apple and Adobe can address the issue together.

Adobe Community Expert / Adobe Certified Instructor

Report · Nov 21, 2017

I upgraded to High Sierra and no longer get the multiple errors...which you could clear and continue working...so that is good...no more errors. but now premier crashes like crazy and is almost unusable. I'll drag a photo to the timeline and drag the handles to expand the time and boom-crash. open, get back working and try something else...boom crash. I'm nearly dead in the water. I'm working on stuff while cringing that any moment I could crash and lose work. aweful. I would NOT upgrade to high sierra.

Report · Jan 24, 2018

Hi ShawnW,

High Sierra is a major OS update. When that happens, I found that you have to reset Adobe folder permissions. It's been my habit since OS X 10.9 and my Mac systems always run well with Premiere. Here's how: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, an...

Please try it.

Thanks,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

Report · Jan 24, 2018

Thanks, I just completed the instructions. I did note however, that next to my user name...how I am logged in, it said read&write but for two other profiles it was read only.

Also after I rebooted I got this Photoshop error. Photoshop does appear to be working though.

My display card is the NVIDIA GeForce GT 750M 2GB

full system specs

Report · Jan 26, 2018

Still crashes like crazy. really annoying.....like I almost have to use another editing tool as a result because I cant stand restarting my project a dozen times while on a deadline. this sucks

Report · Apr 04, 2018

I too have been having this problem on my MacPro5,1 running macOS 10.12.6 + NVIDIA GTX980ti + 780. I think I have found the culprit...it's the VST plugins within the main "Adobe Premiere Pro CC 2018.app" bundle.

When I moved all the .vst plugins in the /Applications/Adobe Premiere Pro CC 2018/Adobe Premiere Pro CC 2018.app/Contents/Plug-Ins/en_US/VSTPlugins" folder, Premiere started up without the barrage of annoying MTLCompilerService error windows.

EDIT: False alarm...after I rebooted, the errors popped up again on startup, as well as when quitting Premiere.

Super annoying.

Report · Dec 18, 2018

Did anyone ever fix this? I have a fresh install of CC 2019 and this is always popping up. 10.12.6 MacBook Pro (Retina, 15-inch, Mid 2015) w/

AMD Radeon R9 M370X 2048 MB

I don't have Nvidia. So OpenCL should be no problem.

Report · Feb 10, 2019

Is there any update on this?

Report · Feb 28, 2019

Wyclef, still running 10.12? Let us know.

Thanks,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

Report · Feb 28, 2019

Yes, I am still on 10.12

Report · Feb 28, 2019

Wyclef,

Try updating to 10.13. I did and I have a similar machine at my home studio. I don't get the warning any more. That said, with newer versions of Premiere Pro - it's time to start thinking about updating your hardware. I've made that realization for myself, as well.

Thanks,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

Report · Feb 28, 2019

I'm still on 10.12.6. and still CONSTANTLY get that error OpenCL or not. Older MacPro with upgraded NVidia GeForce GTX 980

Adobe Community Expert / Adobe Certified Instructor