Skip to main content
Brandon Kraemer
Brandon Kraemer
Known Participant
November 14, 2017
Question

Premiere 2018 is unreliable in it's current form. VERY BUGGY.

  • November 14, 2017
  • 3 replies
  • 1879 views

I am getting constant crashing with 2018 running on older MacPro hardware.   I'm not seeing these same issues with nMP hardware FWIW but I have a small sample size with each setup so far. 

Most crash logs return either adobe backend framework issues for RED Cuda issues in the crash threads details like this:

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

0   com.adobe.Backend.framework   0x0000000104d17824 BE::Transaction::~Transaction() + 68

1   com.adobe.Backend.framework   0x0000000104d280b5 BE::UndoStack::DropActionsAsNecessary(unsigned int) + 101

or this...

Thread 14 Crashed:

0   REDCuda.dylib                 0x000000016448cf58 0x16447b000 + 73560

1   REDCuda.dylib                 0x000000016448d661 0x16447b000 + 75361

or this...

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

0   libsystem_kernel.dylib        0x00007fff95f2af06 __pthread_kill + 10

1   libsystem_pthread.dylib       0x00007fff987024ec pthread_kill + 90

Premiere also crashes upon quit every time.

Regardless of what the issues are.... 2018 is completely untrustworthy in it's current form compared to 2017... it's a liability right now and since you can't save as backwards to 2017 (really Adobe?) you're hosed if you're deep in a project.

I'm about to move my current project to Resolve via XML.... can't work with this nonsense release until it's fixed!!

    This topic has been closed for replies.

    3 replies

    H
    hunt4kelly1
    Known Participant
    November 14, 2017

    I have also had very strange issues with my Workspaces when I have more than one project open, which I've been posting in here Multiple Projects Open Bug?

    Never had so many problems with an NLE as I have with this version.

    Brandon Kraemer
    Brandon KraemerAuthor
    Known Participant
    November 14, 2017

    Never had so many problems with an NLE as I have with this version.

    +1, and that is not hyperbole.

    H
    hunt4kelly1
    Known Participant
    November 21, 2017

    Hey Brandon, Has it got any better for you? I'm still getting lots of crashes and just plain weird stuff. Today I opened a music track which I've been using on a project and for some reason Premiere is only seeing half the track. Bit hard to explain but when I open it in source panel there is only half of the waveform showing in the panel, and it will only play half of it, then it's dead air, yet when I open the track there is no issues with the raw file.

    It's bloomin frustrating.

    H
    hunt4kelly1
    Known Participant
    November 14, 2017

    I am also having major problems with my PC system crashing. I had no issues until I updated to 2018, and since then it's crashing numerous times a day. I've even had Media Encoder crash which has never happened to me before.....Just looking at media encoder now and it looks like it's crashed again. This sux.

    Brandon Kraemer
    Brandon KraemerAuthor
    Known Participant
    November 14, 2017

    I've had some luck on the older MacPro system by disabling CUDA and running with OpenCL.  It's much more stable.  That system has triple GTX 980 Ti cards.

    On my nMP (ican) system with Dual AMD 700 GPUs (not CUDA compatible) I have an issue where Media Encoder will no longer run what is in its queue and that behavior has spread to 2017 Media Encoder as well as 2018, but it was 2018 that first started that behavior.  Switching to Software Only does nothing to clear the issue.

    bk

    R Neil Haugen
    R Neil Haugen
    Legend
    November 14, 2017

    Ouch!

    Everyone's mileage always varies ...
    K
    Katie Houghton
    Inspiring
    November 14, 2017

    I think it may be a hardware issue. I am sure Adobe is working on this. That is why I keep the older software on my system when the new version come out. (Though I have not had any problems with CC18)

    Brandon Kraemer
    Brandon KraemerAuthor
    Known Participant
    November 14, 2017

    It's a software issue (as 2017 had none of these issues) quite possibly relating to how the software integrates with hardware.  Seems like something significant was overlooked or is not supported by Adobe in this 2018 release.

    Having legacy versions on your system is always wise but useless if 2018 can't save backwards to 2017.

    Brandon Kraemer
    Brandon KraemerAuthor
    Known Participant
    November 14, 2017

    Look here Adobe:

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

    0   com.adobe.dvaui.framework      0x0000000100a26336 dvaui::drawbot::OSSurfaceInterface::~OSSurfaceInterface() + 150

    1   com.adobe.dvaui.framework      0x0000000100a26475 dvaui::drawbot::OSSurfaceInterface::~OSSurfaceInterface() + 21

    2   com.adobe.dvaui.framework      0x00000001008255d7 dvaui::controls::UI_DisclosureTriangleButton::~UI_DisclosureTriangleButton() + 199

    3   com.adobe.UIFramework.framework 0x000000010dbe4035 UIF::DisclosureTriangleImpl::~DisclosureTriangleImpl() + 21

    4   com.adobe.UIFramework.framework 0x000000010dbe3434 UIF::DisclosureTriangle::Destroy() + 52

    5   com.adobe.HSL.framework        0x00000001122d6ad2 HSL::ParameterCache::ReturnDisclosure(UIF::DisclosureTriangle*) + 18

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