Premiere Pro CC 2014.2 crashes when "locating media"

The problem;
Premiere Pro CC 2014.2 crashes when "locating media".  I am working on a project that has not given me any problems for the last 200 hours.   About a week ago I notice that the .proj file size was 276mb and found this odd because my largest project to date was never larger than 80mbs.  I thought that the premiere was running slow because of the project size. As luck would have, when my client made their their final changes 2 days ago, I opened the project and premiere would hang on the locating media window and then would crash. I called Adobe and spent an hour on the phone with them to no avail. 
Project workflow
- 700gb of 5d footage
- 20 sequences under 5 minutes
- Dynamically linked files with AE
- Warp Stabilized about a dozen clips of under 5 sec
- On every sequence color correction adjustment layer with  RGB Curves, Three way color corrector and sharpen filter
- I kept old versions of the sequences (I was in version 5 before the crash)
What I have tried;
- Unsuccessfully tried to open auto-save files for this project.
- Successfully opened other older non relevant project
- Removed Mercury playback engine in the project settings
- Cleaned out media cache database through pp in media Preferences
- Manually deleted cache files in /Common/Media Cache Files and /Common/Media Cache
- Tried importing sequences into new .proj file; it would crash as a result.
What "worked".
I was able to open it on another computer. save it under another file name. bring it back to my original computer and open it without problem. I lost about 3 days working through this problem, I missed my deadline. and angered the client.  I was able to use a friends IMAC to "fix" the problem, however I can't always count on him being there if it happens again.
Questions.
- What the hell happened? Why could I open it on one computer and not on the other?
- Is there a way to fix a corrupted .proj files on a PC?
- What should the average file size be, before it becomes unstable? (I'm pretty that my file size was bloated by all the previous versions of the sequences)
Windows 8.1  64bit
Premiere 2014.2
Intel Quadcore i7-4770    3.40GHz
16gb Ram

Hi,
I would suggest the following steps:
http://blogs.adobe.com/kevinmonahan/2014/09/10/premiere-pro-cc-freezing-on-startup-or-cras hing-while-working-mac-os-x-10-9-and-later/
Run a disk permission repair on your boot drive, and
Reset Home Folder permissions and ACLs Error | Apple Support Communities
Thanks,
Rameez

Similar Messages

  • Premiere Pro CC 2014 crashes when loading project file

    Hi guys, any help on this is much appreciated as I have a job due in 18 hours and I'm in big trouble if I can't fix this.
    I've been editing a project in Adobe Premiere Pro CC 2014 (updated to the latest version) and when I tried to access the same file today it is giving me the error message:
    'Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project.'
    I had saved other version files and they all seem to be working properly so I know it's not my HD that is corrupt. In fact my suspicion is that it has something to do with a blur effect i'm using. The only problem is, I can't even access the file to delete the effect as the project file won't open.
    Information about my computer:
    I am using a Macbook Pro
    OS X version 10.9.4
    2.6 Ghz Intel Core i5
    Memory 16 GB, 1600 MHz DDR3
    Any suggestions/comments would be appreciated.

    Guys I solved my own problem - thought I'd share with you how in case anyone else is having this problem -
    I came across this thread
    Premiere Pro CC error message and crash
    which had the suggestion -
    "Do tou have after effects installed? If yes, please try to import the main sequence into it and then export it as premier pro project from file/export ootion and then try to open that in premiere pro."
    This didn't work for me too but I did try and import my existing project into a new project and copy all the files over. Works fine now.
    I don't know if I will have the same issue again tomorrow so I'm going to render out a super high res video before I close premiere just in case

  • Premiere Pro CC 2014 crash when I Click and Drag

    Hi All, I have a problem with Premiere CC 2014 that is driving me crazy!
    The issue is as follows:
    If I try to drag a clip, sequence, effect or transition anywhere within the premiere, it will crash - with "Sorry, a serious error has occurred" message. The program will crash, quit and the saved recovery project is usually healthy (luckily!). BUT, as soon as I've re-started the program, and reloaded the project - or any project for that matter - the problem persists. As soon as I click and drag, Premiere crashes!
    In order to 'reset' this, I have to restart my machine. Once I have done so, I can continue editing as normal for a while (not long, perhaps up to an hour, or so) but eventually, it WILL crash again. I've not been able to work out what I have to do in order to trigger this - it seems random. But once it's happened, only restarting my computer will resolve it - and then only temporarily.
    Here are all the facts:
    The crash ONLY happens when I drag something... This can include moving a clip on the timeline, dragging a clip form the source viewer or project window, dragging an effect or transition.
    The crash happens after I have clicked, as soon as I start to move my mouse.
    I CAN click and drag to extend in and out points on the timeline, and I can do 'insert' edit using the button on the source monitor. No crash here.
    The footage plays fine.
    I am trying this on a CLEAN OS X install, with only Adobe packages installed, to eliminate any potential of interference from other programs. There are no third party plugins or drivers installed. No user data installed either (preferences, photos, documents, etc) - as fresh as it comes!
    I am not running Time Machine in the BG
    My system is: Macbook Pro 2011, 16GB Ram, 1tb SSD, OS X Yosemite 10.10.1. Intel Graphics card, so no option to turn on or off hardware acceleration. It is set to software only.
    I have tested this with projects and footage on an external drive, as well as internal, same issue.
    I noticed the issue had started on, or around 25-27th November 2014.
    Interestingly, I have noticed that once this crash has occurred in Premiere, a similar problem will occur in After Effects as soon as I drag a file or layer... doesn't matter what the layer is. The crash seems less elegant here, I don't get an error message, it just freezes and I have to 'force quit'. Again, the problem persists until the machine is restarted.
    I have been using my macbook and premiere pro cc 2014 on Mavericks for a long time, and had no problems - so I know it should work fine! The only things that changed were an update to Yosemite, I started using Time Machine to make regular backups, I installed a few new fonts and any CC updates that happened in the background... I can rule out most of these because of my fresh install, with no user data, fonts plugins or time machine to confuse matters... It must be an Adobe bug with Yosemite!
    Any ideas?
    Thanks so much in advance!!

    Hi Vince,
    vince_email wrote:
    ...The only things that changed were an update to Yosemite, I started using Time Machine to make regular backups...
    Please check this blog post. Updating from Time Machine can cause this issue: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later).
    Thanks,
    Kevin

  • Premiere Pro CC (2014) crashing when making a sequence

    I just did a clean install of OS X Yosemite and installed Creative Cloud on my 2008 MacPro. Every time I make a new sequence or open a saved Premiere Pro CS6 project, Premiere Pro CC 2014 always crashes. I am not sure what is going on because before I updated OS X from Mavricks, I used Premiere Pro CS6 with no issues at all. Please help! Thanks!
    Here are my MacPro settings:
    Here are the errors I am getting:
    That blank space usually says this:

    Ok I have seemed to "fix" the problem. I have two video cards on my MacPro:
    I have a three monitor setup with two monitors on the 2600 XT and a single monitor on the 6870. I unplugged the two monitors on the 2600 XT and created a new sequence and it didn't crash. Not quite sure what is going on with this because this was never an issue while I was running Adobe Premiere Pro CS6. I still do want to run a three monitor setup but the 6870 doesn't want to support three monitors. Hopefully there is an update from Adobe that will fix this issue.
    Is there a way that Premiere will not try to use the other video card?

  • Premiere Pro CC 2014 crashes when deleting keyframes on photos

    As the title says, I'm getting a crash every time I delete keyframes from photos I've done "Ken Burns" style moves to. It gives me the old "A serious Error has occurred" message and poof.
    This never happened with CS6, CS5.5, CS5, CS 4.5...well...you get the idea!
    Is there a workaround or is this a new bug that needs to be dealt with?
    Next time it happens I will take a screen grab but I have a serious deadline to meet right now.

    Process:         Adobe Premiere Pro CC 2014 [696]
    Path:            /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
    Identifier:      com.adobe.AdobePremierePro
    Version:         8.2.0 (8.2.0)
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [212]
    Responsible:     Adobe Premiere Pro CC 2014 [696]
    User ID:         501
    Date/Time:       2015-01-28 10:11:49.817 -0700
    OS Version:      Mac OS X 10.9.5 (13F34)
    Report Version:  11
    Anonymous UUID:  C952FF8E-A6AA-F0DE-6B82-B28EFDDF79A8
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: EXC_I386_GPFLT
    External Modification Summary:
      Calls made by other processes targeting this process:
        task_for_pid: 2
        thread_create: 0
        thread_set_state: 0
      Calls made by this process:
        task_for_pid: 0
        thread_create: 0
        thread_set_state: 0
      Calls made by all processes on this machine:
        task_for_pid: 2079
        thread_create: 1
        thread_set_state: 0
    VM Region Summary:
    ReadOnly portion of Libraries: Total=624.6M resident=382.1M(61%) swapped_out_or_unallocated=242.5M(39%)
    Writable regions: Total=2.1G written=558.9M(26%) resident=1.2G(55%) swapped_out=0K(0%) unallocated=967.7M(45%)
    REGION TYPE                      VIRTUAL
    ===========                      =======
    ATS (font support)                 32.1M
    ATS (font support) (reserved)         8K        reserved VM address space (unallocated)
    CG backing stores                  21.6M
    CG image                            524K
    CG raster data                       48K
    CG shared images                    204K
    CoreImage                            72K
    Foundation                            4K
    IOKit                             644.0M
    IOKit (reserved)                    268K        reserved VM address space (unallocated)
    Image IO                            816K
    Kernel Alloc Once                     8K
    MALLOC                            547.1M
    MALLOC (admin)                       32K
    Memory Tag 241                      116K
    Memory Tag 242                       12K
    Memory Tag 249                      156K
    Memory Tag 251                       36K
    OpenCL                            474.6M
    OpenGL GLSL                        1664K
    STACK GUARD                        56.1M
    Stack                              25.8M
    VM_ALLOCATE                        76.4G
    VM_ALLOCATE (reserved)              444K        reserved VM address space (unallocated)
    __DATA                             84.4M
    __IMAGE                             528K
    __LINKEDIT                        225.7M
    __NV_CUDA                           456K
    __TEXT                            398.9M
    __UNICODE                           544K
    mapped file                        72.0M
    shared memory                        68K
    ===========                      =======
    TOTAL                              78.9G
    TOTAL, minus reserved VM space     78.9G
    Model: MacPro4,1, BootROM MP41.0081.B07, 8 processors, Quad-Core Intel Xeon, 2.66 GHz, 64 GB, SMC 1.39f5
    Graphics: NVIDIA GeForce GTX 680, NVIDIA GeForce GTX 680, PCIe, 2048 MB
    Memory Module: DIMM 1, 8 GB, DDR3 ECC, 1066 MHz, 0x85F7, 0x463732314755363546393333334700520000
    Memory Module: DIMM 2, 8 GB, DDR3 ECC, 1066 MHz, 0x85F7, 0x463732314755363546393333334700520000
    Memory Module: DIMM 3, 8 GB, DDR3 ECC, 1066 MHz, 0x85F7, 0x463732314755363546393333334700520000
    Memory Module: DIMM 4, 8 GB, DDR3 ECC, 1066 MHz, 0x85F7, 0x463732314755363546393333334700520000
    Memory Module: DIMM 5, 8 GB, DDR3 ECC, 1066 MHz, 0x85F7, 0x463732314755363546393333334700520000
    Memory Module: DIMM 6, 8 GB, DDR3 ECC, 1066 MHz, 0x85F7, 0x463732314755363546393333334700520000
    Memory Module: DIMM 7, 8 GB, DDR3 ECC, 1066 MHz, 0x85F7, 0x463732314755363546393333334700520000
    Memory Module: DIMM 8, 8 GB, DDR3 ECC, 1066 MHz, 0x85F7, 0x463732314755363546393333334700520000
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.100.22)
    Bluetooth: Version 4.2.7f3 14616, 3 services, 15 devices, 1 incoming serial ports
    Network Service: Ethernet 1, Ethernet, en0
    PCI Card: NVIDIA GeForce GTX 680, Display Controller, Slot-1
    PCI Card: NVIDIA GeForce GTX 680, NVDA,Parent, Slot-1
    PCI Card: pci1b4b,9230, AHCI Controller, Slot-2
    PCI Card: pci1b73,1100, USB eXtensible Host Controller, Slot-4
    Serial ATA Device: OWC Mercury Accelsior PCIe SSD, 479.95 GB
    Serial ATA Device: HL-DT-ST DVD-RW GH41N
    Serial ATA Device: WDC WD10EADS-65L5B1, 1 TB
    Serial ATA Device: WDC WD2002FAEX-007BA0, 2 TB
    Serial ATA Device: WDC WD20EADS-00R6B0, 2 TB
    Serial ATA Device: WDC WD20EADS-00R6B0, 2 TB
    Serial ATA Device: MARVELL VIRTUALL
    USB Device: TOURO Mobile 3.0
    USB Device: BRCM2046 Hub
    USB Device: Bluetooth USB Host Controller
    USB Device: Hub in Apple Pro Keyboard
    USB Device: iLok
    USB Device: USB-PS/2 Optical Mouse
    USB Device: Apple Pro Keyboard
    FireWire Device: built-in_hub, Up to 800 Mb/sec
    FireWire Device: SAFFIRE_PRO_40, Focusrite, Up to 400 Mb/sec
    Thunderbolt Bus:

  • Premiere Pro CC 2014 crashing when playing back especially when playing back graphics.

    I updated Premiere Pro to CC 2014 last week and found it crashing a lot when playing back especially when playing back graphics. Has anyone else had this problem?

    More information needed for someone to help... please click below and provide the requested information
    -Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
    What is your exact brand/model graphics adapter (ATI or nVidia or ???)
    What is your exact graphics adapter driver version?
    Have you gone to the vendor web site to check for a newer driver?
    For Windows, do NOT rely on Windows Update to have current driver information
    -you need to go direct to the vendor web site and check updates for yourself
    ATI Driver Autodetect http://support.amd.com/en-us/download/auto-detect-tool
    nVidia Driver Downloads http://www.nvidia.com/Download/index.aspx?lang=en-us

  • Premiere Pro CC 2014 crashing when trying to see a sequence

    This is the error message I keep receiving - 
    [/caravan/releases/2014.09/shared/adobe/MediaCore/Backend/Src/Sequence/PersistentGroupCont ainer.cpp-279]
    The only variant I've seen is when I try opening the same sequence in Premiere Pro CC, not 2014.
    I've tried importing in the exact sequence to a fresh new project and it drops the import altogether. Has anyone seen this happen across multiple versions of cleanly installed Premiere?

    Hi Cityroom,
    This might be helpful: https://forums.adobe.com/thread/1394068?tstart=0
    Thanks!
    Rameez

  • Premiere Pro CC(2014) crashing when copying and pasting clips

    Has anyone found Premiere to hang when copy and pasting clips from one sequence to another, or even within the same sequence.
    Sometimes, it hangs then comes back to life.  Other time I just have to force quit.
    Thanks

    I don't recall reports of such a problem. We'll need more info to attempt to troubleshoot the issue. Start with the prompts on this page: FAQ: What information should I provide when asking a question on this forum? Especially the details on your computer.
    Also, please report the following:
    the types of content in your sequence, particularly in segments you're pasting. The source(s) of the content, the codec(s), the duration of copied segments?
    where the content is stored?
    whether either sequence was imported from a third-party program via XML or the like?
    the sequence settings of both sequences?
    what effects & transitions are in use, particularly in the segments you're pasting?
    what is resource usage before and during the copy/paste operation? Is a CPU getting pegged? Does memory usage spike precipitously?

  • Premiere Pro CC 2014 Crashes When Soundediting.

    Hi,
    I have been editing a film on a PC 64bit, windows 7.1. For some time now.
    It´s perrfectly fine until I started using the Audio Denoiser and EQ effects and doing some
    basic sound editing/mixing whatever you want to call it.
    Simply crashes after a while. A serious error one time (seen that Before!) and
    sometimes just locks canvas and after a while crashes.
    Strange!
    Any solutions to this?

    Thanks! It works fine now!
    Kind of Think I can remember that being an issue Before.
    Can´t remember if it was the CS6 I was running back then.

  • Premiere Pro CC 2014 crashing constantly

    Premiere Pro CC was great. Premiere Pro CC 2014 is not so great!
    Constantly crashing every time I go to render after a while.
    It happens so inconsistently I cannot explain.
    I wish Adobe would see this post and contact me to resolve.
    We pay for 5 seats every month and should not have to deal with software crashing constantly.
    Thanks,
    J

    Hi, I have the same problem too.
    Premiere pro cc 2014 crash constantly. I found problem in the overflow of RAM when I quickly scan (review) my clips on the timeline or resize the clips.
    My configuration:
    Premiere pro cc 8.1; 16Gb RAM; SSD 120(where i store and work with my video); CPU Intel i72700K; Windows 7 Pro x64

  • Premiere Pro 5.5 crashes when importing mpg file

    Premiere Pro 5.5 crashes when importing mpg file.
    I can get the file to import if I first right click the file and tell it to "open in source monitor" then tell it to import.
    When I do this it indexes the file. After it is done indexing is when I can then import the file.
    Should I not just be able to tell it to import and it does the indexing?
    These files that I am tryig to open were with Premiere Pro 4.

    Welcome to the forum.
    What are the specs. of this MPEG file? Might be something in those, that is causing an issue.
    Good luck,
    Hunt

  • Premiere Pro CC 2014 Crashes During Media Export

    Hi, I have diligently applied several of the fixes listed here:
    Re: Premiere Pro CC 2014 freezes frequently and crashes
    However, Premiere Pro CC crashes at about 10% of the video export -- it gets through the audio stuff as far as i can see.

    yeah, checked out the article.
    my computer is not shutting down. premiere is crashing. the media exporter is crashing.
    it gets through the audio then it crashes during the video processing.
    i even tried to hit pause every 2 seconds.
    a test exports fine from premiere 6.0, but i am concerned that 6.0 might crash if i rebuild the whole project.
    hmm i have an idea.
    obviously i would much rather the software worked.

  • Premiere Pro CC 2014 crash and crash, and crash....

    Kevin and all you other Premiere Pro CC people out there.
    How long before Adobe will solve the problem of Premiere Pro crashing over and over again.
    I guess there is no one reading this that could tell me "it works for me".
    So Kevin (staff),
    Here is the 36-line-report you requested from me.
    For your information. Premiere Pro CC 2014_2 and back paddling to 8.0, they all crash.
    Most crashes are freeze on timeline. Thats is, nothing moves, sometime the music track
    just keep going and you can't stop it, so you have to hard quit.
    My power: Mac Pro 2014, 6 core, dubble graphic card, 64 GB memory, 1 TB SS storage
    This is my latest report:
    Process:               Adobe Premiere Pro CC 2014 [717]
    Path:                  /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
    Identifier:            com.adobe.AdobePremierePro
    Version:               8.0.0 (8.0.0)
    Code Type:             X86-64 (Native)
    Parent Process:        ??? [1]
    Responsible:           Adobe Premiere Pro CC 2014 [717]
    User ID:               501
    Date/Time:             2015-04-03 14:55:56.729 +0900
    OS Version:            Mac OS X 10.10.2 (14C1514)
    Report Version:        11
    Anonymous UUID:        3C4BE865-15A1-83C0-2A8F-247384EECB0D
    Time Awake Since Boot: 19000 seconds
    Crashed Thread:        0  Dispatch queue: com.apple.main-thread
    Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes:       KERN_INVALID_ADDRESS at 0x00000000000000c0
    VM Regions Near 0xc0:
    -->
        __TEXT                 0000000100000000-0000000100003000 [   12K] r-x/rwx SM=COW  /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   com.apple.CoreText             0x00007fff8c98db95 TLine::~TLine() + 243
    1   com.apple.CoreFoundation       0x00007fff9105ca9e CFRelease + 526
    2   com.apple.HIToolbox           0x00007fff8d5a0944 TCoreTextLineInfo::~TCoreTextLineInfo() + 34
    3   com.apple.HIToolbox           0x00007fff8d5a0913 TLayoutInfo::Clear() + 51
    4   com.apple.HIToolbox           0x00007fff8d5a078f TCoreTextEngine::Invalidate() + 49
    5   com.apple.HIToolbox           0x00007fff8d59d0a8 TCoreTextEngine::Init(void const*, THIThemeTextInfo const*) + 92
    6   com.apple.HIToolbox           0x00007fff8d59cf00 TThemeTextCache::Create(void const*, THIThemeTextInfo const*) + 460
    7   com.apple.HIToolbox           0x00007fff8d59c8bf DataEngine::GetTextDimensions(void const*, double, HIThemeTextInfo*, double*, double*, double*) + 259
    8   com.apple.HIToolbox           0x00007fff8d59c785 HIThemeGetTextDimensions + 185
    9   com.apple.HIToolbox           0x00007fff8d5e124e HIStandardMenuView::MeasureItemTextWidth(__CFString const*, TextLayout*, __CTFont const*) + 122
    10  com.apple.HIToolbox           0x00007fff8d5e0a3f HIStandardMenuView::GetItemWidth(float, TextLayout*, unsigned char*) + 719
    11  com.apple.HIToolbox           0x00007fff8d5dde02 HIStandardMenuView::GetOptimalSizeSelf(CGSize*, float*) + 878
    12  com.apple.HIToolbox           0x00007fff8d5dda1c HIView::SendGetOptimalBounds(CGRect*, float*, CGSize*) + 416
    13  com.apple.HIToolbox           0x00007fff8d5dd84f HIView::GetOptimalSize(CGSize*, float*, CGSize*) + 45
    14  com.apple.HIToolbox           0x00007fff8d5dd755 HandleCalculateMenuSize(OpaqueEventRef*) + 154
    15  com.apple.HIToolbox           0x00007fff8d58213a MenuData::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 358
    16  com.apple.HIToolbox           0x00007fff8d58098c DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1260
    17  com.apple.HIToolbox           0x00007fff8d57fdce SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 386
    18  com.apple.HIToolbox           0x00007fff8d57fc42 SendEventToEventTargetWithOptions + 43
    19  com.apple.HIToolbox           0x00007fff8d5dd4e4 _CalcMenuSizeOnDevice(MenuData*, unsigned short, unsigned int, CGRect const*, unsigned int) + 763
    20  com.apple.HIToolbox           0x00007fff8d5e1bad GetInitialMenuRect(MenuSelectData*, MenuData*, unsigned char, Point, unsigned short, Rect*, unsigned int*, CGPoint*) + 261
    21  com.apple.HIToolbox           0x00007fff8d5f6f32 GetCurrentMenuRect(MenuSelectData*, unsigned int*, CGPoint*) + 110
    22  com.apple.HIToolbox           0x00007fff8d605890 DrawTheMenu(MenuSelectData*, __CFArray**, unsigned char, unsigned char*) + 582
    23  com.apple.HIToolbox           0x00007fff8d60548c MenuChanged(MenuSelectData*, unsigned char, unsigned char) + 356
    24  com.apple.HIToolbox           0x00007fff8d5f1e36 TrackMenuCommon(MenuSelectData&, unsigned char*) + 1211
    25  com.apple.HIToolbox           0x00007fff8d604fb1 MenuSelectCore(MenuData*, Point, double, unsigned int, OpaqueMenuRef**, unsigned short*) + 510
    26  com.apple.HIToolbox           0x00007fff8d604c5e _HandleMenuSelection2 + 446
    27  com.apple.AppKit               0x00007fff9191b8be _NSHandleCarbonMenuEvent + 277
    28  com.apple.AppKit               0x00007fff917b72f0 _DPSNextEvent + 1843
    29  com.apple.AppKit               0x00007fff917b6730 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 194
    30  com.apple.AppKit               0x00007fff917aa593 -[NSApplication run] + 594
    31  com.adobe.Frontend.framework   0x00000001000c948d FE::MacApplication::RunSelf() + 45
    32  com.adobe.Frontend.framework   0x0000000100047cca FE::Application::Run(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 4058
    33  com.adobe.Frontend.framework   0x00000001000cad44 FE::AppMain(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 276
    34  com.adobe.Frontend.framework   0x00000001000d1f25 FE::Run(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int) + 581
    35  com.adobe.AdobePremierePro     0x00000001000018ac main + 508
    36  com.adobe.AdobePremierePro     0x00000001000016a4 start + 52

    Hi,
    Sorry to hear about the experience. Can you please try this:
    Go to the following locations:
    Location 1: When in Finder, click on Go > Go to Folder > ~/Library/Application Support/Adobe
    Location 2: Go > Go to Folder > ~/Library/Preferences/Adobe
    Location 3: Documents > Adobe
    In all the locations, rename the 'Adobe' folders to 'OldAdobe'
    Launch Premiere, accept the License Agreement and see if it works.
    Note: You will lose your customized workspaces and keyboard shortcuts. Wait for Premiere to generate the media cache the first time you launch the project.
    Also i would suggest you to make this change if the playback issue continues and see if it works better:
    Under File > Project settings > General, change the Video renderer to Mercury Playback Engine software only. Click OK and select "Delete Previews"
    Thanks,
    Rameez

  • Premiere Pro CC 2014 gets stuck on Media Pending.

    Hi there,
    I've been having a bit of trouble with PPCC 2014 opening projects then getting stuck with all my footage and assets and after effects comps just displaying with 'Media Pending'. The program still works, opens, and I can save and click around so it's not crashing but nothing loads unless I force it to relink which obviously isn't great when I'm having to edit multiple large projects. These projects still open just fine on regular old Premiere Pro CC so I will continue using that for the time being.
    Media Encoder is also having an issue with After Effects comps that are in Premiere Pro timelines and only display as 'Media Pending'.
    Fortunately all these issues go away if I reboot my machine and try again straight away, but having to reboot my mac just to open a project or do a export isn't exactly preferable.
    I have a Mac Pro (late 2013) with 10.9.4 with 16gb Ram and a AMD D500 3GB card.
    I'm just wondering if anyone has been suffering with the same issues and has come across any fixes.
    Thanks in advance.

    Here is my post from another thread concerning the same issue:
    I got through Adobe to connect to me remotely to solve this problem twice. They cleaned the cache and preferences and renamed my Adobe folder under applications (don't exactly know how thy did it.) The problem disappeared only to come back after a little while. No video playback, unresponsive buttons - but playable audio, and media pending for all clips. I told them to report this to tech support. This was about a month ago but no updates still..I know I hadn't had this issue neither with CS6 nor with CC.
    I am currently rendering my project after changing the sequence's editing mode to Quicktime ProRes Proxy to see if it will help. Preview is still preview but as you said maybe the issue is to be with preview settings set to i-frame mpeg. I have read about the mpeg importer plugin to be an issue in previous versions of premiere pro concerning issues with media pending but i might be wrong.
    After changing the sequence settings to Prores Proxy (or if you don't have these codecs installed you may try another codec or google "Prores codec install" and have them installed) the problem cleared away. I have looped the timeline and played it over and over for a couple of hours without the issue surfacing.
    For Adobe support and for others to know here is a wiki concerning the issue in CS5. FAQ:Why does my clip show as "media pending"? - Adobe Premiere Pro

  • Adobe Premiere Pro CC 2014 Crashing very often! Please Help!

    Hello,
    I am currently editing my first feature on Adobe Premiere Pro CC 2014 and it is currently up to date.
    I am editing on a iMac 27in, late 2013 brand new computer.
    Processor: 3.5 GHz Intel Core i7
    Memory 32GB 1600 MHz DDR3
    Graphics: NVIDIA GeForce GTX 780M 4096MB
    System: OSX Yosemite V 10.10.1
    The project is located on a 8TB G Drive
    7200 RPM
    High Performance ThunderBolt drive.
    Details of the project:
    I am currently working on a fine cut of 5K Red Footage that is being cut in the RAW.
    I work at 1/2 quality settings and have no lag.
    The timeline includes limited stacked video files and various mp3 audio files.
    The Problem:
    Lately, the program will randomly quit or freeze up 4-5 times during an 5-6 hour edit session.
    Many times it is random, however, it seems to happen often if I accidentally click on the end of a clip on the timeline and it goes to switch into trimming mode. 
    Also, it will randomly go into the "pinwheel of death" out of nowhere followed by "Adobe CC is not responding."
    My project file is just about 15MB now.
    What is causing this reoccurring problem?
    How can I make it happen less?  I have scoured the forums and found similar articles but no helpful solutions.
    I have recently turned auto save on to save every 2 minutes because there have been more than one occasion where I lost A LOT of work because of this issue.
    I am about two weeks out from picture lock delivery and this issue is driving me crazy and loosing me a ton of time.
    Please help or let me know if any more additional information can help solve the issue.
    I have sent in well over 25 error reports already.
    Thanks,
    Thomas.

    I think I may have found the solution...
    I completely removed the Premiere Pro folder under User > Documents > Adobe and so far it seems to have solved the problem.
    I of course backed up my projects and than deleted this folder. So far it seems it worked.
    I'll know for sure in a day or two, but after constantly crashing, Premiere hasn't crashed for the last 4-5 hours of work.
    Goran

Maybe you are looking for