Forum Replies Created

  • Cassian Hall

    September 12, 2017 at 11:04 am in reply to: Serious error crashing Prem Pro continuously

    Thanks for this Greg, I’m going to read with interest!

  • Cassian Hall

    September 12, 2017 at 11:03 am in reply to: Serious error crashing Prem Pro continuously

    Hi Peter,

    I think I followed the instructions – but tell me if I got it wrong! I think this is the relevant part of the crash log, although there are quite a few crash logs to choose from ( I chose at random):

    Process: Adobe Premiere Pro CC 2017 [853]
    Path: /Applications/Adobe Premiere Pro CC 2017/Adobe Premiere Pro CC 2017.app/Contents/MacOS/Adobe Premiere Pro CC 2017
    Identifier: Adobe Premiere Pro CC 2017
    Version: 11.1.2 (11.1.2)
    Code Type: X86-64 (Native)
    Parent Process: ??? [1]
    Responsible: Adobe Premiere Pro CC 2017 [853]
    User ID: 501

    Date/Time: 2017-09-06 18:10:42.940 +0100
    OS Version: Mac OS X 10.12.6 (16G29)
    Report Version: 12
    Anonymous UUID: 41A6C210-1DBE-E051-E2F9-92F3132AC575

    Time Awake Since Boot: 30000 seconds

    System Integrity Protection: enabled

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

    Exception Type: EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: EXC_I386_GPFLT
    Exception Note: EXC_CORPSE_NOTIFY

    Termination Signal: Segmentation fault: 11
    Termination Reason: Namespace SIGNAL, Code 0xb
    Terminating Process: exc handler [0]

    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0 com.adobe.Frontend.framework 0x0000000100999641 FE::Application::AttemptPanicProjectSave() + 17
    1 libsystem_platform.dylib 0x00007fffb495cb3a _sigtramp + 26
    2 ??? 000000000000000000 0 + 0
    3 com.apple.FinderKit 0x00007fffabb3b32b TThreadSafeCache::Retrieve(unsigned long long const&) const + 21
    4 com.apple.FinderKit 0x00007fffabb3b117 TRunAfter::Cancel(unsigned long long) + 95
    5 com.apple.FinderKit 0x00007fffab95e0da TMDQueryAliasNode::CloseQuery() + 22
    6 com.apple.FinderKit 0x00007fffab95dea9 TMDQueryAliasNode::~TMDQueryAliasNode() + 29
    7 com.apple.FinderKit 0x00007fffab95e164 TMDQueryAliasNode::~TMDQueryAliasNode() + 14
    8 com.apple.FinderKit 0x00007fffab9457e2 TCustomNode::ReleaseCustomNodeCallback(OpaqueNodeRef*, void*) + 148
    9 com.apple.desktopservices 0x00007fffab0b6ed6 TNode::~TNode() + 228
    10 com.apple.desktopservices 0x00007fffab0b6d97 -[FITNode dealloc] + 25
    11 com.apple.desktopservices 0x00007fffab0b6d76 -[FITNode releaseUnderMonitor] + 39
    12 com.apple.desktopservices 0x00007fffab096f44 NodeDisposeNodeRef + 234
    13 com.apple.FinderKit 0x00007fffab94b93f TFENode::~TFENode() + 17
    14 com.apple.FinderKit 0x00007fffab965c0f std::__1::__vector_base::~__vector_base() + 47
    15 libsystem_c.dylib 0x00007fffb47e2178 __cxa_finalize_ranges + 332
    16 libsystem_c.dylib 0x00007fffb47e24b2 exit + 55
    17 libdyld.dylib 0x00007fffb474d23c start + 8

    Thread 0 crashed with X86 Thread State (64-bit):
    rax: 0x48535641e5894855 rbx: 0x0000000000000000 rcx: 0x00007fffb487c186 rdx: 0x0000000000000000
    rdi: 0x00007fffab94574e rsi: 0x00007fff5fbff278 rbp: 0x00007fff5fbff340 rsp: 0x00007fff5fbff2e8
    r8: 0x0000000000000040 r9: 0x0000000100477aa8 r10: 0x00007fffb487c186 r11: 0x0000000000000202
    r12: 0x000000000000000b r13: 0x00007fffbd6bf3c0 r14: 0x0000000100a5af80 r15: 0x0000000000000009
    rip: 0x0000000100999641 rfl: 0x0000000000010206 cr2: 0x0000000100bb1882

    Logical CPU: 0
    Error Code: 0x00000000
    Trap Number: 13

  • Cassian Hall

    September 11, 2017 at 4:52 pm in reply to: Serious error crashing Prem Pro continuously

    Thanks Eric, I appreciate you taking the time to answer. I think you’re right that the memory is an issue, and I am now looking at upgrade possibilities and will be now facing the Mac v PC issue.
    I found a crazy workaround for now, that involved importing the sequence into After Effects and then re-exporting only the section I need back to Prem Pro. I had to redo all the transitions and effects, but it is no longer crashing for now – a result that will carry me through tomorrow. But the real issue is probably my old mac running short of memory and corrupting files (it’s my best guess). I need 4k editing capabilities which I don’t currently have, so a new system is on the cards (bank allowing).

    Best,

    Cassian

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