Premiere Pro CC 2018 constantly crashing

[adams28687784]

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

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

[Nexahs1138]

The update came out this week, of course there's going to be issues in that time, everyone knows that when there's an update for something you leave it until things have settled down

Was the wall of text really necessary?

[UncannyFilms]

In terms of the wall of text, I wasn’t sure how much of the log to post.

in terms of the update, I actually stated:

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

This began, across all my project files, before the update was released.

[Nexahs1138]

Well the log is only going to be relevant to Customer Care, no one on the forums is going to read that.

Have you tried running as Admin?

[Kevin-Monahan]

Well the log is only going to be relevant to Customer Care, no one on the forums is going to read that.

It's no problem, but I do prefer that Mac users trim the log. Here's how. FAQ: How do I post a Mac OS X crash log?

Thanks,
Kevin

[d2pro]

Wrong wrong wrong. I read it and it resolved my issue faster than any forum post I've ever read, ever. Did I mention how wrong you are?

[Mactavius]

This was a WELL documented issue with Premiere Pro CC 2017 and Adobe stayed relatively mute on it.  Like OP, I was hoping the release of 2018 would fix the issue.  Sadly no.  Many of us have been fighting this demon for well over a year, so it's not a new bug.

[Devyn Brugge]

macm20163476  wrote

This was a WELL documented issue with Premiere Pro CC 2017 and Adobe stayed relatively mute on it.  Like OP, I was hoping the release of 2018 would fix the issue.  Sadly no.  Many of us have been fighting this demon for well over a year, so it's not a new bug.

What is the well documented issue you are referring to? Is it related to CUDA?

[Kevin-Monahan]

Hi MacM,

This was a WELL documented issue with Premiere Pro CC 2017 and Adobe stayed relatively mute on it.  Like OP, I was hoping the release of 2018 would fix the issue.  Sadly no.  Many of us have been fighting this demon for well over a year, so it's not a new bug.

Both my Mac and PC are running smoothly with both versions, so I'm not sure of the "issue" you are having. With memory leaks? Let us know more details so we can assist you.

Thanks,
Kevin

[Kevin-Monahan]

BTW, are you still facing this issue? Let us know.

Thanks,
Kevin

[stevenprobets]

What a silly comment.

The causes of crashes will never been known if people don't report them and bring them up in forums.

The more thorough the better. If we all just sat around saying 'ah well, there will be an update that will fix everything' NOTHING will get fixed!

My problem with 2018 is that it just crashes. I have been editing my project all day with no problems. I left Premeire open while I ate my dinner. I didn't touch anything and when I came back it had crashed. Shall I report this or just hope some other mug will and it will be fixed in the next update?

[Nexahs1138]

The forums isn't the place to be reporting issues, you need to tell Customer Support.

[ReelAir]

Well it sure helped me out...

[Kevin-Monahan]

Hi stevenprobets,

I left Premeire open while I ate my dinner. I didn't touch anything and when I came back it had crashed. Shall I report this or just hope some other mug will and it will be fixed in the next update?

What kind of footage? Have you repaired Adobe folder permissions? Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, an...

Thanks,
Kevin

[rcoutophoto]

I gave all permissions, did everything right, spent hours researching something that could help and did not succeed. The program simply closes informing you that an unexpected error has occurred. I think I'll take the advice of a friend and migrate to Final Cut.

[Devyn Brugge]

Our office is also moving over to Final Cut Pro X. I can't believe it!

[WavezEditor]

What info should be we be giving in these forums that will help to get this fixed ?

[nct2176]

Nexahs1138  wrote

The update came out this week, of course there's going to be issues in that time, everyone knows that when there's an update for something you leave it until things have settled down

Was the wall of text really necessary?

Oi! Be helpful next time.  Can your computer not handle that much text? Go be angry about something important.

[Nexahs1138]

Huh, that's exactly what I'd suggest to the OP, why make a complaint about a new update having bugs? It's to be expected.

Unless I was using a super computer there is no issue with the text other than it is an eyesore.

[Ryan_Mackfall]

what are you going on about?! The forum is the place to discuss issues. Stop having a go at someone trying to get a problem fixed, what exactly are you doing on this post other than having a go at someone?

Literally the most counterproductive person I've encountered on here. The sharing of data and information is how creators and business owners get over issues. Please remove yourself from this convo and consider why you're REALLY here getting angry and offensive at people. I doubt very much it's anything to do with the original post.

[d2pro]

Are you for real? The post was really helpful and instantly solved my issue. You have no idea what you're talking about.

[anthony_gc]

Who are you to talk to another person that way.  If you don't want to help, then don't.  But no one needs your rude remarks.

[leonardjfrench]

Wow, what a rude person. We come here for troubleshooting information, not your attitude.

[stripe17]

Premiere Pro cc2018 was crashing for me until I updated Red Giant Universe and Magic Bullet Film.

[stevenprobets]

I updated Universe but not Magic Bullet. I’ll try that.

The point of reporting crashes on forums