Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Premiere CS6 crashes consistently with GPU Acceleration enabled

  • Premiere CS6 crashes consistently with GPU Acceleration enabled

    Posted by Chris Taylor on June 8, 2013 at 8:50 pm

    To start – the last week has been a technological nightmare. Premiere would not stop crashing and I couldn’t output anything above SD resolution without it blasting me with “serious errors”. Seeming how I graduate film school in a few days and have a massive amount of content to turn in before then, I could really use expedited assistance.

    Here’s the tech overview:
    – editing primarily natively with Redcode
    – 10 min program length
    – other codecs being used including Animation and DV NTSC
    – iMac 2.5GHz i5, 16GB RAM, AMD Radeon 6750M Graphics Card
    – Mountain Lion 10.8.4

    After a few days of troubleshooting and forum research (trashing prefs, trashing renders, repairing disk, clean install of OSX and CS6) I finally switched the rendering/playback setting from GPU to Software Only and *viola* I can finally export an entire sequence. Granted it takes a couple hours to do so, but it’s all I can do for now.

    My only assumption is a graphics card malfunction, outdated driver or incompatible hardware. I would gladly pay nearly any amount at this point to cease the Premiere crashing and resume a happy life, because this frankly is driving me to the loony bin.

    – Chris

    Chris Taylor replied 12 years, 11 months ago 4 Members · 8 Replies
  • 8 Replies
  • Bret Williams

    June 9, 2013 at 4:48 am

    I don’t believe that GPU is officially supported by Premiere. There is a hack to make it work, but my experience has been that all you’ll get is instability.

  • Chris Taylor

    June 9, 2013 at 6:22 am

    If it’s in their menu options, I’d say they’ve officially decided to support it. They wouldn’t include it to cater exclusively to their hacking customers. Plus that was a default setting. It took me several hours of forum searching to even find where and what it was.

  • Al Bergstein

    June 9, 2013 at 9:55 am

    Have you tried transcoding everything bur Red to Prores? Maybe theres a bug in their handling of one of the codecs?beyond that, I’d say theres a bug in the drivers with your specific config, given that turning it off the GPU stops it. Also, is there an ATI driver upgrade?

    Al

  • Bret Williams

    June 9, 2013 at 8:13 pm

    That’s interesting, because as of March. None of the GPUs in a 2011 iMac were supported. I bought a 2012 and its not supported either.

  • Bret Williams

    June 10, 2013 at 1:41 am

    My bad. Should be supported. It’s one of two ATI cards supported at all by Adobe. Only appears on the lower end iMac and the higher end iMac cards are unsupported, like the 6970m. Apparently they won’t be supported in the CCloud version either. Two years of testing isn’t enough I guess.

  • David Mcgavran

    June 10, 2013 at 11:40 pm

    Have you checked the card list in CC? Very comprehensive. You need 1 Gig of ram though. For the crashes can you send us a crash log?

    thanks

    Dave

    ———————————————————————————————————
    David McGavran, Adobe Systems Incorporated
    Senior Engineering Manager Adobe Premiere Pro
    ———————————————————————————————————

  • Chris Taylor

    June 16, 2013 at 8:13 pm

    Sure, my pleasure:

    Process: Adobe Premiere Pro CS6 [470]
    Path: /Applications/Adobe Premiere Pro CS6/Adobe Premiere Pro CS6.app/Contents/MacOS/Adobe Premiere Pro CS6
    Identifier: com.adobe.AdobePremierePro
    Version: 6.0.2 (6.0.2)
    Code Type: X86-64 (Native)
    Parent Process: launchd [127]
    User ID: 501

    Date/Time: 2013-06-16 13:05:13.423 -0700
    OS Version: Mac OS X 10.8.4 (12E55)
    Report Version: 10

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

    Exception Type: EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

    VM Regions Near 0:

    VM Region Summary:
    ReadOnly portion of Libraries: Total=463.6M resident=323.0M(70%) swapped_out_or_unallocated=140.6M(30%)
    Writable regions: Total=1.5G written=1.2G(81%) resident=1.4G(89%) swapped_out=0K(0%) unallocated=167.6M(11%)

    REGION TYPE VIRTUAL
    =========== =======
    (null) (reserved) 40K reserved VM address space (unallocated)
    ATS (font support) 31.9M
    ATS (font support) (reserved) 4K reserved VM address space (unallocated)
    CG backing stores 13.6M
    CG image 320K
    CG shared images 192K
    CoreImage 8K
    CoreServices 2404K
    IOKit 44.2M
    IOKit (reserved) 1536K reserved VM address space (unallocated)
    MALLOC 370.7M
    MALLOC guard page 64K
    Memory tag=240 4K
    Memory tag=242 12K
    Memory tag=249 156K
    Memory tag=251 28K
    OpenCL 52K
    OpenGL GLSL 1808K
    OpenGL GLSL (reserved) 128K reserved VM address space (unallocated)
    STACK GUARD 56.1M
    Stack 23.7M
    VM_ALLOCATE 1.0G
    __DATA 34.9M
    __IMAGE 528K
    __LINKEDIT 158.1M
    __TEXT 305.5M
    __UNICODE 544K
    mapped file 147.3M
    shared memory 14.9M
    =========== =======
    TOTAL 2.2G
    TOTAL, minus reserved VM space 2.2G

  • Chris Taylor

    June 16, 2013 at 8:16 pm

    As for the card list, it is a compatible card – if that’s what you were inferring.

    – Chris

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy