Skip to main content
vitaliyz
vitaliyz
Participating Frequently
February 27, 2018
Question

Tired of Premiere Pro CC 2018 Crashes

  • February 27, 2018
  • 3 replies
  • 730 views

ok i am freaking tired of constant crashes every 10-20 min....

can't finish my work....

yes i have read all forums about that

set permissions... render to software and metal nothing works etc.etc.etc.etc.

this just freaks me out...

here is the full error log sry for spam and wall of text....

Process:               Adobe Premiere Pro CC 2018 [84299]

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.1 (12.0.1)

Code Type:             X86-64 (Native)

Parent Process:        ??? [1]

Responsible:           Adobe Premiere Pro CC 2018 [84299]

User ID:               503

Date/Time:             2018-02-27 02:04:40.017 +0100

OS Version:            Mac OS X 10.13.3 (17D102)

Report Version:        12

Anonymous UUID:        0B7A8836-87CD-023A-7286-A3DDE66D3B3D

Sleep/Wake UUID:       59D4DA13-98B1-4102-9152-73303304003E

Time Awake Since Boot: 110000 seconds

System Integrity Protection: enabled

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

Exception Type:        EXC_BAD_ACCESS (SIGBUS)

Exception Codes:       KERN_PROTECTION_FAILURE at 0x0000000101bda058

Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Bus error: 10

Termination Reason:    Namespace SIGNAL, Code 0xa

Terminating Process:   exc handler [0]

VM Regions Near 0x101bda058:

    __TEXT                 00000001019cc000-0000000101bd2000 [ 2072K] r-x/rwx SM=COW  /Applications/Adobe Premiere Pro CC 2018/Adobe Premiere Pro CC 2018.app/Contents/Frameworks/MBCProvider.framework/Versions/A/MBCProvider

--> __DATA                 0000000101bd2000-0000000101be0000 [   56K] rw-/rwx SM=COW  /Applications/Adobe Premiere Pro CC 2018/Adobe Premiere Pro CC 2018.app/Contents/Frameworks/MBCProvider.framework/Versions/A/MBCProvider

    __DATA                 0000000101be0000-0000000101be2000 [    8K] rw-/rwx SM=PRV  /Applications/Adobe Premiere Pro CC 2018/Adobe Premiere Pro CC 2018.app/Contents/Frameworks/MBCProvider.framework/Versions/A/MBCProvider

[crash report deleted by mod, only post on request Adobe engineer]

This topic has been closed for replies.

3 replies

vitaliyz
vitaliyzAuthor
Participating Frequently
March 12, 2018

bump

vitaliyz
vitaliyzAuthor
Participating Frequently
February 28, 2018

i think this might help also...

i don't know anymore...

vitaliyz
vitaliyzAuthor
Participating Frequently
February 28, 2018

just got report from crash analyzer

i made the suggested actions and lets see how it works now...

ill keep updating

Text Crash

This crash appears to have occurred when displaying text. A common cause of this is a duplicate or corrupt font.

Suggested Actions

  • Use Font Book's Resolve Duplicates and Validate Font functions to determine the problematic font, then remove it.
  • Clear your application font cache with Housekeeper.
  • Clear your system font cache with System Toolkit.
  • If this crash occurred while entering text, try removing invalid characters such as / ? \ : * | " and remove any foreign or non-alphanumeric characters.

Relevant Line

10 com.apple.CoreText 0x00007fff3e32361d TTypesetterAttrString::TTypesetterAttrString(__CFAttributedString const*) + 33

Report generated by Crash Analyzer in Pro Maintenance Tools
vitaliyz
vitaliyzAuthor
Participating Frequently
February 28, 2018

another error =)

Graphics Card

This crash appears to have been caused by an issue with your graphics card or graphics drivers.

Common causes:

Using a large number of layered tracks.
Putting lots of filters on a single clip, especially if that clip is a long-GOP format such as XDCAM or H.264.
Running Adobe Creative Suite on an underpowered graphics card. Running out of graphics memory.

Suggested Actions

Render your sequence.
Resize any large images in your project to keep them below 4000 x 4000 pixels.
Try switching o  clip thumbnails in your sequence to improve stability. Update your operating system, as Apple includes new graphics drivers with each macOS point update.
Consider purchasing a more powerful graphics card.
Since this crash is often caused by overworking the computer, consider the following to minimize the strain on your system:

Don't edit MPEG-2, H.264, XDCAM or HDV in the timeline - convert them to a more editing-friendly codec such as ProRes.
Export dynamic-linked After E ects projects to QuickTime movies. If you must have dynamic-linked After E ects projects in your timeline, make sure they are not too complex.

Don't use your system drive as a scratch disk.
Make sure your scratch disk has enough throughput to playback the video format you are using plus 20% for overhead. Also make sure it has at least 20% free disk space on it.
If you are using multiclips, remember that each camera angle plays back simultaneously, so you need fast enough disks to play back all of your multiclip angles at once.
If you are using any third-party filters in your sequence, make sure they are compatible with your version of Premiere Pro. It's worth checking with the manufacturer for an update.

More Information

This crash is directly related to an issue with your graphics card drivers. Drivers are included in Mac macOS point releases so please update to the latest version of your OS.

Relevant Line

                 

1 com.apple.GeForceGLDriver 0x00007 f373dd34d 0x7 f370e0000 + 3134285

Report generated by Crash Analyzer in Pro Maintenance Tools

sanchesto
sanchesto
Known Participant
February 27, 2018

Recommending installing and running Digital Rebellion's Crash Analyzer to get more insight on the cause of the crash.

Pro Maintenance Tools - Digital Rebellion

vitaliyz
vitaliyzAuthor
Participating Frequently
February 28, 2018

ok i installed it and ruined all the tests etc. adobe still HANGS itself after some time....

this is crazy strange i work with the ssd based files so there shouldn't be any speed problems in reading and such

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices