Premiere Pro CC 2018 constantly crashing

Report · Oct 19, 2017

Hi, first time poster who's hoping someone can help me out.

I've used Premiere for the last 3 years without any problems, but over the last week it's begun constantly crashing. I can get about 5 minutes out of it, before the serious error message. The log's below, and what I've done to try and combat is:

Reset Preferences

Cleaned Media cache files

Opened a new project, and imported the old one in

Uninstalled and reinstalled it

This has been a problem with the 2017 version, and the 2018 one I upgraded to yesterday.

My MacBook Pro's specs are:

Retina, mid 2014

Processor: 2.5 GHz Intel Core i7

16gb Memory 1600 MHZ DDR3

Graphics: NVDIA GE Force GT 750M 2GB

Intel Iris Pro 1536 MB

The footage is just 1080p, so nothing too taxing, and with no effects. Any help would be hugely appreciated!

This is the full log:

Process: Adobe Premiere Pro CC 2018 [1296]

Path: /Applications/Adobe Premiere Pro CC 2018/Adobe Premiere Pro CC 2018.app/Contents/MacOS/Adobe Premiere Pro CC 2018

Identifier: com.adobe.PremierePro.CC12

Version: 12.0.0 (12.0.0)

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Adobe Premiere Pro CC 2018 [1296]

User ID: 501

Date/Time: 2017-10-19 18:12:41.363 +0100

OS Version: Mac OS X 10.13 (17A405)

Report Version: 12

Anonymous UUID: 62F30C99-8942-1B1D-9A30-3694040A50FD

Time Awake Since Boot: 2000 seconds

System Integrity Protection: enabled

Crashed Thread: 100 Dispatch queue: opencl_runtime

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)

Exception Codes: 0x0000000000000001, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Illegal instruction: 4

Termination Reason: Namespace SIGNAL, Code 0x4

Terminating Process: exc handler [0]

Application Specific Information:

*** CFRetain() called with NULL ***

Thread 100 Crashed:: Dispatch queue: opencl_runtime

0 com.apple.CoreFoundation 0x00007fff4d64b222 CFRetain + 114

1 com.apple.GeForceGLDriver 0x00007fff482a646d 0x7fff47fa9000 + 3134573

2 com.apple.GeForceGLDriver 0x00007fff482a55b0 0x7fff47fa9000 + 3130800

3 libGPUSupportMercury.dylib 0x00007fff65daef11 gldLoadTexture + 194

4 com.apple.GeForceGLDriver 0x00007fff482c0d02 gldLoadTexture + 223

5 com.apple.opencl 0x00007fff55bea783 0x7fff55bb5000 + 219011

6 com.apple.opencl 0x00007fff55bf1449 0x7fff55bb5000 + 246857

7 com.apple.opencl 0x00007fff55bd436d 0x7fff55bb5000 + 127853

8 com.apple.opencl 0x00007fff55bd79fc 0x7fff55bb5000 + 141820

9 libdispatch.dylib 0x00007fff74bf2f64 _dispatch_client_callout + 8

10 libdispatch.dylib 0x00007fff74c0742b _dispatch_queue_serial_drain + 635

11 libdispatch.dylib 0x00007fff74bfa30e _dispatch_queue_invoke + 373

12 libdispatch.dylib 0x00007fff74c08117 _dispatch_root_queue_drain_deferred_wlh + 332

13 libdispatch.dylib 0x00007fff74c0bef0 _dispatch_workloop_worker_thread + 880

14 libsystem_pthread.dylib 0x00007fff74eb6033 _pthread_wqthread + 980

15 libsystem_pthread.dylib 0x00007fff74eb5c4d start_wqthread + 13

Model: MacBookPro11,3, BootROM MBP112.0142.B00, 4 processors, Intel Core i7, 2.5 GHz, 16 GB, SMC 2.19f12

Graphics: Intel Iris Pro, Intel Iris Pro, Built-In

Graphics: NVIDIA GeForce GT 750M, NVIDIA GeForce GT 750M, PCIe, 2 GB

Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020

Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134), Broadcom BCM43xx 1.0 (7.77.37.0.1a1)

Bluetooth: Version 6.0.0f7, 3 services, 27 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en0

PCI Card: pci1b21,612, AHCI Controller, Thunderbolt@196,0,0

PCI Card: pci1b21,612, AHCI Controller, Thunderbolt@11,0,0

Serial ATA Device: APPLE SSD SM0512F, 500.28 GB

Serial ATA Device: HGST HDS724040ALE640, 4 TB

USB Device: USB 3.0 Bus

USB Device: Apple Internal Keyboard / Trackpad

USB Device: BRCM20702 Hub

USB Device: Bluetooth USB Host Controller

Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1

Thunderbolt Device: G-DRIVE with Thunderbolt USB 3.0, G-Technology, 1, 7.2

Thunderbolt Device: G-DRIVE with Thunderbolt USB 3.0, G-Technology, 3, 7.2

Report · Oct 26, 2017

Hi AdamS,

First, update CUDA drivers in System Preferences. Then, ensure that you are set to "OpenCL" in Project Settings for GPU acceleration. Is it working now?

Thanks,
Kevin

Report · Oct 27, 2017

Both source and program monitors go to white and will not play video when I do that.

Model Name: Mac Pro

Model Identifier: MacPro5,1

Processor Name: 6-Core Intel Xeon

Processor Speed: 3.06 GHz

Number of Processors: 2

Total Number of Cores: 12

L2 Cache (per Core): 256 KB

L3 Cache (per Processor): 12 MB

Memory: 64 GB

NVIDIA GeForce GTX 689 8.0.90 driver

ATI Radeon HD 2600 XT

El Capitan 10.11.6

Report · Dec 01, 2017

Hi MGorga,

Both source and program monitors go to white and will not play video when I do that.
NVIDIA GeForce GTX 689 8.0.90 driver
ATI Radeon HD 2600 XT

That usually means that you're running out of VRAM. How much VRAM is in that NVIDIA GPU? I am unfamiliar with that model. You might try this if you're crashing: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, an...

Thanks,
Kevin

Report · Oct 31, 2017

by updating CUDA drivers do you mean have the most recent driver for your video card?

Report · Jun 12, 2018

From what I learned go to Nvidia Geforce and download update drivers as this will then give you options of CUDA as well as Mercury - It will also explain your system requirements depending on graphics cards you use. Am totally New but learning slowly as i go on. Drivers | GeForce

Report · Nov 20, 2017

Dear,

I really need help, I am a subscriber to Premiere CC 2018, but I can not work on it on my MacBook I have the NVIDIA GEFORCE 750M 2GB video card but when using it in OpenCL simply Premiere works a little and closes informing error and it happens all the time , I updated CUDA, I uninstalled and installed again is the problem persists, the fact is that I signed with you and I can not cancel in 12 months, but if there is no improvement I will have to prove via judicial that the program does not work and to be compensated, as I am being harmed by something that does not work.

Report · Dec 01, 2017

Hi RCoutoPhoto,

I would recommend that you repair Adobe folder permissions. Then, begin a new project. If you have AVCHD footage, try transcoding the footage first.

Thanks,
Kevin

Report · Oct 26, 2017

I have updated all my plug ins and cleared cache's, I still just get random crashes.

It can happen at anytime, but significantly when I leave Premiere for a short time (like making tea). It happens on any project.

My system is 100% updated.

macOS Sierra 10.13 (17A405)

iMac (Retina 5K, 27-inch, Late 2015)

4 GHz Intel Core i7

32 GB 1867 MHz DDR3

AMD Radeon R9 M395X 4 GB

Mode

Report · Nov 01, 2017

Mine is doing the same, on a similar system with maybe just slightly higher spec, what a pain, it just randomly say (not responding) and I have to force 'end task' with task manager

Just received my renewal price from Adobe, which I will not be doing if this isn't sorted quickly, this has cost me loads of time and money this week. For something so reliable to become so utterly useless after an update is unacceptable, especially at the prices I gladly pay for good tools. And before anyone else says 'don't use until bumps ironed out bla bla, fairly sure that is Adobe's job whilst they are developing the update?

Tired, harassed, and looking at Final Cut and the dreaded Mac as we speak!

Report · Dec 01, 2017

Spuup,

Mac or PC? Which OS? What kind of footage?

Thanks,
Kevin

Report · Nov 18, 2017

High Severity!

I cannot get any of the Adobe media products to launch on Mac OS 10.11.6. They all crash!

I even tried remoiving and reinstalling CC and Primier and the "work-around" suggested by Adobe in this post Adobe Premiere Pro CC, Adobe Media Encoder CC, Adobe Prelude CC crash | Mac OS but to no avail. Adobe, please fix immediately!

I had to launch CC on a windows machine to continue working on my project but I'm certain that option is not available to most CC users.

Report · Nov 25, 2017

Adobe Hi Adam I have the same problem and thank you for posting this as Adobe obviously monitors these posts and will ask you for more info inevitably. Any time I ask Adobe customer care for help its a waste of time. I am on a new iMac thats fully loaded and I cannot take this anymore. It crashes 10 times a day!!! It happens especially after I render or export media but also just regular editing. Adobe has a lot of nerve to charge so much and deliver such a flawed product. What other industry gets away with this. Notice how Adobe Staff came into the middle of your post and disappeared. Not a further whisper. They have nothing to offer and you saved yourself the hassle of asking. I am going back to Final Cut out of sheer necessity and it helps that Final Cut & Motion's total price only buys me one year of Adobe Premiere and After Effects.

Report · Nov 27, 2017

I am feeling the same way.

I have the same specs as stevenprobets and have been working on Calisthenics Concert DVD for a new client and I am now at "copy of copy of copy of copy of copy"....of my repaired projects file. It never used to crash this much. What have you done to this program Adobe?

Not happy!

And I can't see the point of paying AUD60 per month for this rubbish as this is the main program I use other than After Effects and PhotoShop.

Report · Dec 01, 2017

AdamS, and anyone else on the thread that uses Mac,
I run an underpowered Macbook Pro on macOS Sierra for my own projects. I never crash. So your problem is not with Premiere Pro, necessarily.

The top troubleshooting step for random crashing and crashing on launch for macOS it to reset your Adobe folder permissions. As these do become reset after updating macOS, I do this after every major macOS update—for good measure, I also perform the same steps for every Premiere Pro update.
- It cannot hurt your system, only help.
- Perform the steps in this blog post and post back if you find some success in halting your crashing issues.
- Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, an...
The other top tip to prevent performance issues is to never update a CC2017 project, instead, import the old project into a brand new CC 2018 project, if you must.
If you have problems with your system "freezing" after leaving it conform your footage, consider transcoding the footage before starting to edit with it. You can use ProRes, Cineform, or DNxHD/HR. It's possible that macOS is not adequately decoding footage which requires Dolby decoders (usually AVCHD).
If none of the above works, switch GPU processing to another mode, or run Premiere Pro GPU acceleration to "Software Only" mode—found in Project Settings.

Cheers,
Kevin

Report · Jan 21, 2018

Hi Kevin,

I have problems with Crashing at closing and also at rendering. I don't get as many crashes last playback/working on the project. but it permanently crashes at closing and rendering. What do you think the problem can be?

I'm running Mac OS High Sierra with Premiere pro 2018, I have an iMac pro 10 cores, 64GB ram, 2 tb HD and the 16GB graphic card.

Please Advise since I'm in the middle of a project.

Thanks!

-----------

Here is the Crash SHORT Crash report:

Process: Adobe Premiere Pro CC 2018 [9658]

Path: /Applications/Adobe Premiere Pro CC 2018/Adobe Premiere Pro CC 2018.app/Contents/MacOS/Adobe Premiere Pro CC 2018

Identifier: com.adobe.PremierePro.CC12

Version: 12.0.0 (12.0.0)

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Adobe Premiere Pro CC 2018 [9658]

User ID: 501

Date/Time: 2018-01-20 08:40:12.147 -0500

OS Version: Mac OS X 10.13.2 (17C2205)

Report Version: 12

Bridge OS Version: 2.0 (15P2064)

Time Awake Since Boot: 34000 seconds

Time Since Wake: 1900 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 com.adobe.Frontend.framework 0x00000001023c8781 FE::Application::AttemptPanicProjectSave() + 17

1 dyld 0x00000001087a7056 ImageLoaderMachOCompressed::resolveTwolevel(ImageLoader::LinkContext const&, char const*, ImageLoader const*, ImageLoader const*, unsigned int, bool, bool, ImageLoader const**) + 86

2 com.adobe.boost-threads.framework 0x0000000100036bcb boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 59

3 com.adobe.boost-threads.framework 0x000000010003689a boost::thread::join_noexcept() + 122

4 com.adobe.dvacore.framework 0x000000010020e2e0 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::Flush() + 448

5 com.adobe.DisplaySurface.framework 0x000000011a2a004d DS::TerminateDisplay() + 61

6 com.adobe.DisplaySurface.framework 0x000000011a2946e9 DS::Terminate() + 281

7 com.adobe.PlayerMediaCore.framework 0x000000013e21cca7 xRendererEntry + 727

8 com.adobe.VideoRenderer.framework 0x00000001070f43c3 ML::AcceleratedRendererModule::CallAcceleratedRendererModule(int, void*, void*) + 195

9 com.adobe.VideoRenderer.framework 0x00000001070f3974 ML::AcceleratedRendererModule::~AcceleratedRendererModule() + 84

10 com.adobe.VideoRenderer.framework 0x00000001070f3a4e ML::AcceleratedRendererModule::~AcceleratedRendererModule() + 14

11 com.adobe.VideoRenderer.framework 0x00000001070f5457 ML::AcceleratedRendererModuleFactory::~AcceleratedRendererModuleFactory() + 71

12 com.adobe.PluginSupport.framework 0x0000000106a765c8 std::__1::__tree<std::__1::__value_type<dvacore::utility::Guid, ASL::InterfaceRef<ML::IPluginModuleFactory, ML::IPluginModuleFactory> >, std::__1::__map_value_compare<dvacore::utility::Guid, std::__1::__value_type<dvacore::utility::Guid, ASL::InterfaceRef<ML::IPluginModuleFactory, ML::IPluginModuleFactory> >, std::__1::less<dvacore::utility::Guid>, true>, std::__1::allocator<std::__1::__value_type<dvacore::utility::Guid, ASL::InterfaceRef<ML::IPluginModuleFactory, ML::IPluginModuleFactory> > > >::destroy(std::__1::__tree_node<std::__1::__value_type<dvacore::utility::Guid, ASL::InterfaceRef<ML::IPluginModuleFactory, ML::IPluginModuleFactory> >, void*>*) + 56

13 com.adobe.PluginSupport.framework 0x0000000106a765b9 std::__1::__tree<std::__1::__value_type<dvacore::utility::Guid, ASL::InterfaceRef<ML::IPluginModuleFactory, ML::IPluginModuleFactory> >, std::__1::__map_value_compare<dvacore::utility::Guid, std::__1::__value_type<dvacore::utility::Guid, ASL::InterfaceRef<ML::IPluginModuleFactory, ML::IPluginModuleFactory> >, std::__1::less<dvacore::utility::Guid>, true>, std::__1::allocator<std::__1::__value_type<dvacore::utility::Guid, ASL::InterfaceRef<ML::IPluginModuleFactory, ML::IPluginModuleFactory> > > >::destroy(std::__1::__tree_node<std::__1::__value_type<dvacore::utility::Guid, ASL::InterfaceRef<ML::IPluginModuleFactory, ML::IPluginModuleFactory> >, void*>*) + 41

14 com.adobe.PluginSupport.framework 0x0000000106a765b9 std::__1::__tree<std::__1::__value_type<dvacore::utility::Guid, ASL::InterfaceRef<ML::IPluginModuleFactory, ML::IPluginModuleFactory> >, std::__1::__map_value_compare<dvacore::utility::Guid, std::__1::__value_type<dvacore::utility::Guid, ASL::InterfaceRef<ML::IPluginModuleFactory, ML::IPluginModuleFactory> >, std::__1::less<dvacore::utility::Guid>, true>, std::__1::allocator<std::__1::__value_type<dvacore::utility::Guid, ASL::InterfaceRef<ML::IPluginModuleFactory, ML::IPluginModuleFactory> > > >::destroy(std::__1::__tree_node<std::__1::__value_type<dvacore::utility::Guid, ASL::InterfaceRef<ML::IPluginModuleFactory, ML::IPluginModuleFactory> >, void*>*) + 41

15 com.adobe.PluginSupport.framework 0x0000000106a76564 ML::PluginLoaderRegistry::Shutdown() + 132

16 com.adobe.PluginSupport.framework 0x0000000106a76c16 ML::PluginSupport::Shutdown() + 38

17 com.adobe.SweetPeaSupport.framework 0x0000000106b0357e ML::SweetPeaSupport::Shutdown() + 30

18 com.adobe.VideoRenderer.framework 0x00000001071b0a31 ML::VideoRenderer::Shutdown() + 97

19 com.adobe.EAMedia.framework 0x0000000117be7ca7 EAMedia::Shutdown() + 247

20 com.adobe.Mezzanine.framework 0x000000010e55a911 MZ::Initializer::PrivateImpl::~PrivateImpl() + 209

21 com.adobe.Mezzanine.framework 0x000000010e550a1e MZ::Initializer::PrivateImpl::~PrivateImpl() + 14

22 com.adobe.Frontend.framework 0x000000010246b1a9 FE::(anonymous namespace)::MZInitializer::~MZInitializer() + 41

23 com.adobe.Frontend.framework 0x0000000102471377 FE::Initializer::PrivateImpl::~PrivateImpl() + 167

24 com.adobe.Frontend.framework 0x000000010246872e FE::Initializer::PrivateImpl::~PrivateImpl() + 14

25 com.adobe.Frontend.framework 0x000000010249a2f7 FE::AppMain(boost::shared_ptr<ASL::Module> const&, std::__1::basic_string<unsigned short, std::__1::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 423

26 com.adobe.Frontend.framework 0x000000010249b77d FE::Run(boost::shared_ptr<ASL::Module> const&, std::__1::basic_string<unsigned short, std::__1::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int) + 653

27 com.adobe.PremierePro.CC12 0x0000000100007bb0 main + 896

28 libdyld.dylib 0x00007fff7ba2a115 start

Report · Jan 21, 2018

The crashing at closing the app is another everlasting bug which Im also experiencing with Premiere, not just this current version.

I believe it could be related to which panels you have open. I noticed that when the Lumetri panel is open when you close the app the crash is more likeley to happen. Basically Premiere wont close down all the way but gets stuck and can onle be closed by force quitting the app.

Ive had remote support sessions with Adobe support agents about this, but the problem was never solved. I experienced it on a current Macbook Pro with 16GB Ram and Im experiencing it on my 2017 iMac 40GB Ram , its doesnt matter which renderer , it happens with both Metal and Open CL , no difference.

Report · Jan 21, 2018

Yes, Same here... It happens all the time. If I want to render a long piece I have to do it it multiple parts, otherwise it just keeps on crashing and quitting. very frustrating

Report · Jan 22, 2018

Ok SCHMOLLYWOOD!

You are right about closing with the lumetry panel open. Every time is open, it crashes at closing. if I close the panel before closing, it quits fine... Solved that.... well, sort of..

Now what could the program crashing and quitting while rendering... Anybody, any idea?

Thanks!

Report · Dec 04, 2017

Is there something up with CUDA and OpenCL — I am unable to edit without CC 2018 crashing every minute if I use GPU acceleration in this version of Premiere Pro. Although, I can export project in Media Encode with CUDA no problem.

Model Name:	Mac Pro
Model Identifier:	MacPro5,1
Processor Name:	6-Core Intel Xeon
Processor Speed:	3.46 GHz
Number of Processors:	1
Total Number of Cores:	6
L2 Cache (per Core):	256 KB
L3 Cache:	12 MB
Memory:	64 GB
Processor Interconnect Speed:	6.4 GT/s

Chipset Model:	NVIDIA GeForce GTX 1070
Type:	GPU
Bus:	PCIe
Slot:	Slot-1
PCIe Lane Width:	x16
VRAM (Total):	8191 MB
Vendor:	NVIDIA (0x10de)
Device ID:	0x1b81
Revision ID:	0x00a1
ROM Revision:	VBIOS 86.04.50.00.70
Metal:	Supported

CUDA Driver Version: 9.0.222

NVIDIA Web Driver: 378.05.05.25f03

Report · Dec 05, 2017

Guys, here's the deal. When this — happens (every time I update), I just chat with someone at Adobe, give them control of my computer and let them fix it. You pay for this monthly, just let them do it. I chatted with someone yesterday and now my 2018 is working fine. I couldn't get customer care over the weekend so I did all of the changing of permissions, updating, etc. and nothing worked. Save yourself the headache and use the customer care that you're paying for.

Moderator Warning: Please do not use profanity. It is against community guidelines.

Report · Dec 11, 2017

I was just trying that - I found that thread too. I'm going to file a bug report.

Report · Dec 19, 2017

Having the exact same issues. Definite memory leak. I even get the classic cursor stutter before the program (and sometimes computer) crashes...please take note Adobe! This needs to be fixed ASAP.

Running Premiere Pro CC 2018 on a MacPro5,1 on High Serra (10.13.2).

Report · Dec 19, 2017

Yes they had memory leaks on 2017 and now once again? They need to employ a memory leak specialist before releasing new versions it seems!

I put my memory setting in prefs to 'memory' rather than 'performance'. The crashes have gone down BUT still crashes randomly (Media Encoder included). They are so random I cannot send any information about the processes leading upto the crash. Pointless someone from Adobe remote desk-toping my iMac to find out the problem. I have gone through EVERY step mentioned (clearing cache, resetting Premiere on load up, reinstalling etc etc) but still get crashes all the time.

What I am absolutely pipped about is that there has been no updates since the release of 2018 version of Premiere and this stuff should have been fixed by now.

My system:

macOS 10.13.2 (17C88)

iMac (Retina 5K, 27-inch, Late 2015)

4 GHz Intel Core i7

32 GB 1867 MHz DDR3

AMD Radeon R9 M395X 4 GB

Report · Dec 19, 2017

So sorry for you, man.

Let's all hope that we will get a decent christmas upgrade for Premiere. What also helped me, like you mentioned, was to put the memory prefs to "memory" instead of performance. The RAM is still peaking sometimes while I'm feeding Adobe with data but at least it's not crashing anymore.

Report · Dec 20, 2017

The only thing left to do is to file a bug report. So please use the following website: Feature Request/Bug Report Form . It's kinda the only way to help them help us - even if it will take a loooong time.

Adobe Community

Premiere Pro CC 2018 constantly crashing

1 Correct answer