Premiere Pro CC 2014 hangs up on loading importerquicktime.prm
Then it also gives the error message "could not find any capable video play modules."
My system:
HP Elitebook 8570P, Windows 7 Pro, 64 bit
Intel Core i7-3740QM @ 2.7GHz
8G RAM,
GPU: AMD Radeon HD 7500M/ 7600M Series
4G memory
I've been researching this for a couple of days now and the fixes for this are all over the map. I've seen "Run Premiere Pro as Admin," I do. "Update your video drivers," I have, etc. I'm running Late November, 2014 driver per AMD's utility. I've seen lot's of other stuff, that dives down into minutiae, like edit PP's list of supported drivers...[waves hands]...none of that crap works, ok?
Nothing gets PP to load past the message "Loading ImporterQuickTime.prm." I've also installed the latest vesion of QT, by the way. So I have a top-tier (for its day) GPU, and a brand new installation of PP. What gives? Why won't this load?
Any thoughts? Thanks!
found these you can try, if you haven't already
Premiere Pro CC crashes on Launch
Adobe Premeire CC7 crashes on load
some threads report uninstall/reinstall of premiere works. can also use the cleaner tool if you do try that.
Use the CC Cleaner Tool to solve installation problems
Similar Messages
-
Premiere Pro CC 2014.2 Crashing while loading project...
When trying to open Premiere project the program opens and looks like it will load and then crashes.
If I create a new project Premiere opens and I can import footage but as soon as I try to play footage in the preview window or drop it in the timeline the program crashes as well.
I am working on a Windows 7, 64-bit, i7, 8GB ram, 1TB multiple partitioned hard drive. My Graphics card is, Intel(R) HD Graphics 4600 - Driver Version: 9.18.10.3204
My Error Log is:
Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
Faulting module name: MXF_SDK_4.4.33_vs10.dll, version: 4.4.33.0, time stamp: 0x534d772c
Exception code: 0xc0000005
Fault offset: 0x00000000000bdc55
Faulting process id: 0x378c
Faulting application start time: 0x01d02c3625e455c1
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\MXF_SDK_4.4.33_vs10.dll
Report Id: b1b66e81-9829-11e4-95ce-c4346b64bc4f
I can't figure out what the faulting module is.
I just installed CC 2014.2 3 days ago. It all worked fine until yesterday when Premiere started crashing. I restarted the system - same issue. I uninstalled and reinstalled Premiere2014.2 - same issue. Premiere seems to be the only faulting application. Everything else (Ps, Ae, Lr, Id, Au, Ai) appears to still be working.
My version of CS6 (Purchased before getting a creative cloud membership not downloaded through CC) is also still working properly.
Thanks for the help.Update: I updated my Graphics Card Driver to a more recent version. Restarted computer and reopened Premiere and similar crash happened. I went through to get some more crashes and had different crash reports. The faulty module is not always the same.
Problem Event Name: APPCRASH
Application Name: Adobe Premiere Pro.exe
Application Version: 8.2.0.65
Application Timestamp: 5486db4a
Fault Module Name: devenum.dll
Fault Module Version: 6.6.7600.16385
Fault Module Timestamp: 4a5bded7
Exception Code: c0000005
Exception Offset: 00000000000016a0
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: ec5a
Additional Information 2: ec5adb2545b190cc19da7bdfa78d5bf1
Additional Information 3: 6e59
Additional Information 4: 6e59168cf9de1a4a9616903b4a4ba1e1
Problem Event Name: BEX64
Application Name: Adobe Premiere Pro.exe
Application Version: 8.2.0.65
Application Timestamp: 5486db4a
Fault Module Name: OpenCL.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 50eb1a5b
Exception Offset: 000007fee84516a0
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: a527
Additional Information 2: a527a6af76c2b04cfd1fc255c66e5364
Additional Information 3: 21c7
Additional Information 4: 21c71ffc516aa3806e495b8080bd51fe
Both of those are different from the original posted report.
I did have some success following these instructions.
Premiere Pro CC 2014.1 has stopped working - Win 7 64 bit
It appears I do not have a graphics card that is compatible with the mercury engine. I have had three successful tests and one crash since I selected Renderer: "Software only"
I plan to upgrade to a Nvidia card or the supported Intel Iris Card.
This seams to be the issue but I am hesitant to use CC 2014.2 for the time being because I don't know if it will crash randomly and CS6 is working fine. The second error code with "Fault Module Name: OpenCL.dll_unloaded" seems to be directly related to the graphics card and rendering processes. I will update as I learn more.
Please comment with any suggestions or resolutions you have had. -
Premiere Pro CC 2014 keeps freezing when loading projects from Premiere Pro CC
Hi everyone,
I'm reporting this issue in case someone else would have the same problem.
I just downloaded the 2014 version of Premiere Pro CC, and when I'm loading a project from Premiere Pro CC into CC2014 I have the software freezing and being unable to even play the loaded sequences. It seems that dynamic link is having trouble linking the CC and the CC2014 version of Premiere Pro.
Until now the only solution I found was to kill the process of the software and start it again, after 8 times I got my sequence loaded alright, then sometimes it is freezing again, killing process, starting software again, and so on. Does anyone has the same problem ?
I'm running a Windows 7 Ultimate PC with 12Go RAM dedicated only to Premiere Pro.
Cheers,
VincentHi Vincent,
I feel your pain, you are not alone. Here are my machine specs and my very frustrating situation, if anyone has any idea as to how I should move forward, I would really appreciate the input/advice...
iMac - 27" Late 2013
Processor 3.4 GHz Intel Core i5
Memory 12 GB 1067 MHz DDR3
Graphics NVIDIA GeForce GTX 780M 4096 MB
Software OS X 10.9.4 (13E28)
I'm having similar issues that began when I installed Premiere Pro CC 2014, and actually got worse with the latest update/release. The majority of my projects worked fine at first, but the update last week ended that quickly. I did what I know I never should do and updated Adobe CC while completing a project on a deadline. I thought some of the fixes would help me complete the project sooner. Needless to say, the deadline has passed, my client is pissed enough to not pay me or hire me again and I'm stuck with an almost-there version that I can't export correctly because of this software. This is my problem, not Adobe's, but I didn't expect such a detrimental update to halt my operation.
After doing some research, I found that some plugins could be the cause of some specific editing issues, mainly due to incorrect or inaccessible folders - who knows if its Dynamic Link, CC apps or 2014 apps. I concluded that my issue at the time was a plugin permissions issue on the Adobe "Preference" Folder, so I reset the permissions on the folder so that CC and 2014 apps would be able to access its contents without any problems. This was the wrong decision. For some reason, resetting this folders permissions also effected the main HDD, it's Kernel Text files and their respective permission. I could not boot my machine, just got the Apple and spinning wheel until I had to power down. I ended up on the phone with 3 different AppleCare reps who helped me at least be able to turn the machine back on and access my desktop/files, apps, etc. Outside of this, no one could offer anything other than "Uninstall the problematic application, reboot, reinstall, etc..." or "Backup your files and reimage the HDD." When I mentioned the recent CUDA driver update for my graphics card (NVIDIA GeForce GTX 780M 4096 MB now running CUDA Driver Version: 6.0.51), it was like they had never heard of graphics cards being used in their machines.
Resetting permissions on Adobe Preference Folder...
This is what I read would get the CC and 2014 apps communicating correctly so that they could utilize my plugins. There is a problem, I believe, in that their are TOO MANY locations where Adobe folders/components live. There are 3 "Preferences" folders that I found, and I don't know which effects what process, but the folder I changed permissions on clearly effects the operation of all of the CC & 2014 apps I had installed, as well as my HDD. Kernel Extensions and the entire system.
Based on my perceived effects of the Preference folder, I needed to uninstall everything, run the Adobe CC Cleaner Tool, download/install just the 2014 releases and see if that resolved the issue. I'm not downloading CC apps, the 2014 releases should run fine on their own. I've yet to confirm this with Adobe, as what I've read has simply said to install the new release next to the CC apps, rather than on top of, as traditional update releases work. Anyway, one by one, I reinstalled the 14 apps that I use on a regular basis on a "clean" machine with no trace of previous Adobe apps.
After reinstalling (without any plugins), I was at least able to open Premiere Pro from the Application folder and work for a few minutes before both Program and Source monitors froze and had to force quit the app. If I try to open the Project File by double clicking it in the Finder, SpeedGrade opens up instead of Premiere Pro - never seen that before. I also had to force quit to end that process and reopen in Premiere instead of SpeedGrade.
So back to Premiere, if I do have success in opening a project in the right application, Premiere freezes - if not immediately, eventually it will just stop responding. The video clips, sequence segments and UI freeze, but the audio will keep playing until I force quit. When I force quit, Premiere Pro doesn't close entirely. The UI closes, but the process still runs. I've even force quit from Finder, force quit again from the Dock, Shut Down the machine, restarted and Premiere Pro will still be open, but "Not Responding", so I force quit again and open the project. Just now, I opened PP, made minor edits to a sequence, sent it to Media Encoder, exported, but the video I tested exported without audio. I force quite PP twice just before that and it is still running now, but again, it is "not responding".
Ultimately, none of this works, nor have my attempts at resolving these many issues. One thing I know is that there is something VERY WRONG with either the latest release/update to 2014 apps, the Preference folder or the permissions that were changed.
As I mentioned previously, and what I think is a major oversight by someone at Adobe, is that for some reason the permission changes to ONE Adobe folder also effected my entire system and Macintosh HD. Some Kernel Extension files went missing, which is never good and should not happen when resetting folder permissions, so I believe my issues are far greater than the faulty Adobe CC 2014 applications, and is the cause of many of my problems right now. If I can't get things sorted soon, I'm going to reimage my HDD and start from scratch. As much as I would like to avoid this, I really have no choice if I want to get back to work and not lose clients over inexplicable technology issues.
If I find a solution, I will repost, but I think Adobe has to make some serious fixes on this release before anything is resolved entirely. I pay them monthly and rely on their software and platform to work without issue, which is foolish - I know, but I've used CC since it was introduced and it has work well enough until now.
Is there anyone at Adobe that can offer some advice?? -
Premiere Pro CC 2014 hangs on export
I opened a project that worked on the previous version and everything played fine in the 2014 update, rendering previews and smooth playback with no problems. When I go to export it hangs. The sequence is full of ProRes 4444 footage with the sequence settings and previews set to the same codec. I'm trying to export a ProRes 4444 master file.
What I've tried :
- Switching between CPU and GPU rendering
- Render previews and having "match sequence settings" and "use previews" checked
- Render directly without using previews
One thing to note is opening the same project in Premiere Pro CC ( not 2014 ) with the same settings exports without any problems. Glad I didn't uninstall.
System Specs :I'm now getting inconsistent behavior. Exporting in-process is very slow, with a normally 1-2 min export taking 30min - 2 hours for both GPU and Software modes.
I tried unchecking Import Sequences Natively in AME and it stalled out using OpenCL. Tried again in AME with Software Only and it worked normally. Just for fun I tried again in AME with OpenCL and it worked. To test further I enabled Import Sequences Natively again in AME and it works normally for both GPU and Software Only modes. Going back to exporting in-process still doesn't work.
The original CC ( non 2014 ) release never had this problem, and CC 2014 didn't have this problem until the latest update. While this is still pretty broken, at least I can get an export if the stars align through AME. -
Premiere Pro CC 2014 hangs - Problems with MTS files?
Hello all,
So I've read the other MTS file posts on here about problems importing. I had this issue initially but moved the folder and it worked.
I got into my project and every now and then I would get this lagging, where Premiere Pro would still play, but the cursor would be frozen, and anything I click on wouldn't highlight... can't scroll etc. This seems to happen when the fan in my mac kicks up.
It has gotten to the point now where I can't edit the project at all because this happens about 3 minutes in each time. Works fine for a few, then fan kicks up and everything starts lagging and freezing. What's weird is I found a part on the screen, that if I click it, the screen updates to what I just did. SO WEIRD.
THIS DOES NOT HAPPEN ON ANY OTHER PROJECT. And this project isn't even that big. So I highly doubt it's a computer performance issue as I've worked on RED RAW and Prores 4444 files on my macbook pro (which I'm on now) with no issues.
Long story short I've tried about everything, and feel the only solution is to transcode to prores and start all over with the edit (which would be brutal) but I've already completed so much work! Does anybody have experience with this or a work around?
Thanks!Hi Kevin,
Thanks for responding.
I was given a drive with the RAW files on them. I originally just used finder and dragged and dropped into Premiere, since that's what I've always done... but since the issue I'll start using what you mentioned.
Did NOT update the project. Started it on CC 2014.
I tried importing the sequence into a different project and the same issue is occurring. But below I've given more info as to my problems. I'm really concerned I'm going to have to start it all over again. I recently transcoded all files to Prores 422 (hq) in case that's what I need to do. But I'm really hoping there's something I can do to resolve this. Though I have a feeling it's the .MTS files causing issues.
What version of Premiere Pro?
Premiere Pro v8.1.0
What operating system? This should include specific minor version numbers, like "Mac OSX v10.6.8"---not just "Mac".
OS X 10.9.5
What kind(s) of source footage?
AVCHD... I went about "show package contents" until revealing the .MTS files.
What were you doing when the problem occurred?
Editing. Noticed in the beginning, but as the sequence as gotten longer the problem became more persistent, until now it's ALL THE TIME... and the computer fan kicks up right away like it's struggling with playback.
What other software are you running?
Shut down all other programs so Premiere is just running. Still happens. All other projects have been working fine but this is the first with .MTS.
Do you have any third-party effects or codecs installed?
No.
Tell us about your computer hardware. Be especially certain to tell us about third-party I/O hardware (e.g., AJA, Matrox, Blackmagic, MOTU).
None.
Are you using Mercury Playback Engine GPU Acceleration?
Yes.
Does the problem only happen with your final output, with previews, or both?
Everything. Screen lags and freezes with anything. It still plays back without interruption, but my cursor won't move, windows won't update, I can't scroll anywhere unless clicking the top part of Premiere (then it magically updates what I did a moment ago).
Help! -
Importing Final Cut XML Hangs Premiere Pro CC 2014
I am posting this more as a question as to how to report hangs or console reports of PP crashes.
I have a Final Cut Pro project that I wanted to migrate to Premiere Pro using the XML route. When I import the XML from Final Cut, the app hangs with a series of console messages. I think it can't import the DVCPro HD audio and many of the filters used in the Final Cut Project also cause this hang.
On import, a rectangle dialog box appears with no content in it - just a white box. Then the pinwheel of death.
Here are some of the console messages:
11/21/14 10:50:24.289 AM Adobe Premiere Pro CC 2014[1051]: Error loading /Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHDAudio: dlopen(/Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHDAudio, 262): no suitable image found. Did find:
/Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHDAudio: no matching architecture in universal wrapper
11/21/14 10:50:24.290 AM Adobe Premiere Pro CC 2014[1051]: Cannot find function pointer NewPlugIn for factory C5A4CE5B-0BB8-11D8-9D75-0003939615B6 in CFBundle/CFPlugIn 0x115488460 </Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin> (bundle, not loaded)
11/21/14 10:50:30.419 AM Adobe Premiere Pro CC 2014[1051]: Unable to find filter reference documentation "".
11/21/14 10:51:20.658 AM Adobe Premiere Pro CC 2014[1051]: NSAlert is being used from a background thread, which is not safe. This is probably going to crash sometimes. Break on void _NSAlertWarnUnsafeBackgroundThreadUsage() to debug. This will be logged only once. This may break in the future.
11/21/14 10:51:41.000 AM kernel[0]: Sandbox: sandboxd(1088) deny mach-lookup com.apple.coresymbolicationd
11/21/14 10:51:42.102 AM sandboxd[1088]: ([279]) coreaudiod(279) deny file-read-data /Library/Audio/Plug-Ins/Components/A52Codec.component
This also generates an Adobe Premiere Pro hang log in the console system diagnostics.Sort of a work around I am testing:
I have a cool script to open FCPro projects in AE. Sort of a free Automatic Duck. I was going to do this:
Remove all effects and proprietary tracks in FCPro, as some cause problems with this script. Trial and error here.
Use the free script FCP2AE to export to AE (it's hard to find now)
Open the timeline in AE via the script FCP2AE
Export that from AE as PPProCC 2014 project
Open in PPCC2014
That may work, it may also work just to remove all effects and then save the XML and open in PP CC 2014. Again sometimes it does work. The simpler the FCPro project the better.
Another option
I was able to open the FCPro audio only OMF in Audition. Then I exported via XML FCPro format from Audition and this opened the audio tracks in PPCC2014. The stereo tracks were broken and placed on two mono tracks so you'll have to address that one. -
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 -
Why does Premiere Pro CC 2014 renders incredibly slow?
Dear Premiere Pro experts
I created a movie with Adobe Premiere Pro CC 2014 and I have serious performance issues when it comes to export the movie.
The first 10% renders pretty fast and takes 1 hour. Then it takes for every additional 1% about 4 hours! (never rendered it to finish so far, 14% max so far)
Here are some facts that might help to isolate the problem:
Project:
Length: 24 minutes in total, splitted into several sequences (up to 4 minutes) and arranged on a "main-sequence"
Input: Cineform AVI files, 1080p, 59fps (I converted GoPro 3+ footage (3D!) using GoPro Studio to the Cineform format for further processing)
Desired Output: Same as input, preserving 3D (Render 3D Intermediate)
Effects used: Warp-Stabilizer (default settings) and Auto-Color (smoothing 1-2 sec) on almost every clip.
Hardware / Software:
i7-3770K @3.5 GHZ (Quadcore)
16 GB RAM
NVIDIA Geforce GTX 970 (also tried with a ATI Radeon R9 290X)
Windows 8.1
SSD for OS and programs, RAID 0 for media files and project, separate drive for rendering output.
Then I tried to render using AME using the same settings. The whole video rendered in about 14 hours what is acceptable in my case. There problem here is that the 3D gets lost, even if I selected "Render 3D Intermediate". The picture for the left eye is the same as the one for the right eye. This is not happening when I do a direct export. But the direct export get almost stuck at around 10%.
There is almost no difference in choosing Software-Rendering and GPU. Also, the GPU has almost no load. Premiere Pro uses the CPU for about 45% (total usage 65%) and takes up 5-9 GB of memory (total usage 65%). Disk usage at around 14b/s.
I think there are two problems. One is that AME renders differently (no 3D) and the other is that the direct export takes way too long.
Can someone help me with any of these problems?
Thank you,
MartinI did some additional research and found out, that the slow rendering happens with this combination:
- Auto-Color using Temporal Smoothing
- Render 3D Intermediate
Without rendering the 3D intermediate, Temporal Smoothing is not a problem. And without temporal smoothing, Rendering 3D Intermediate is not a problem.
Might this be a problem in the codec or in Premiere? -
Audio-Problem with Adobe Premiere Pro CC 2014 by using long Clips in AVC-Intra Codec (4Gb Border)
Hello
We own a Panasonic camera (AJ-PX5000G) and we film in 1080p50 with the AVC-Intra100 Codec. When importing longer clips in Premiere Pro, the video is fully loaded, but the waveform of the sound ends at the Time Code 00:02:28:35.
Sometimes the sound could be played after this Timecode but otherwise there is no audio. Even if we use the same clip several times we see that it works sometimes and sometimes not. It looks random.
We also tried to import the Clips with Adobe Prelude directly from the P2-Card but there are the same problems.
The Clips in 1080p50 AVC-Intra100 have a bitrate of 227Mbps. After 2 Minutes and 28 Seconds 4Gb are written on the P2-Card and the Camera starts a new picture file and 4 sound files..
It looks like Adobe Premiere Pro has problems with the correct relation of the files that all get together to one clip.
Is there anybody who can confirm this problem? Can anybody help me with this Premiere Problem?
Dennis
(Workstation: Dell Precision T3600, Intel Xeon E5-1620 @ 3.60 GHz, 16 GB RAM, Windows 7 Professional 64-bit, Service Pack 1, Premiere Pro CC 2014.1 (Build 8.1.0) )
Mediainfo of the P2-Cards:
General
Complete name : \CONTENTS\VIDEO\0068T7.MXF
Format : MXF
Format profile : OP-Atom
Format settings : Closed / Complete
File size : 3.92 GiB
Duration : 2mn 28s
Overall bit rate : 227 Mbps
Encoded date : 2014-10-15 13:33:41.000
Writing application : Panasonic P2 2.0
Writing library : Panasonic P2 2.0
Video
ID : 2
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High 4:2:[email protected]
Format settings, CABAC : No
Format settings, GOP : N=1
Format settings, wrapping mode : Clip
Codec ID : 0D01030102106002-0401020201323104
Duration : 2mn 28s
Bit rate : 227 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 50.000 fps
Standard : Component
Color space : YUV
Chroma subsampling : 4:2:2
Bit depth : 10 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 2.193
Stream size : 3.92 GiB (100%)
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Mediainfo Audio-Datei P2-Card:
General
Complete name : \CONTENTS\AUDIO\0068T700.MXF
Format : MXF
Format profile : OP-Atom
Format settings : Closed / Complete
File size : 13.6 MiB
Duration : 2mn 28s
Overall bit rate mode : Constant
Overall bit rate : 770 Kbps
Encoded date : 2014-10-15 13:33:41.000
Writing application : Panasonic P2 2.0
Writing library : Panasonic P2 2.0
Audio
ID : 3
Format : PCM
Format settings, Endianness : Little
Format settings, wrapping mode : Clip (AES)
Codec ID : 0D01030102060400
Duration : 2mn 28s
Bit rate mode : Constant
Bit rate : 768 Kbps
Channel(s) : 1 channel
Sampling rate : 48.0 KHz
Bit depth : 16 bits
Stream size : 13.6 MiB (100%)Hi,
we have the same problem!
It is not possible to play audio with the AVC-Intra100 Codec fluently.
Can anybody help?
Thanks,
Anja -
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 RamHi,
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 -
Exporting to Media Encoder crashes Premiere Pro CC 2014
Greetings,
I am experiencing a problem with premiere off and on. Right now it is an on problem. When I am exporting from Premiere Pro CC (and CC 2014) it will intermittently crash Premiere. I have tried this with several different audio and video formats (AVI [Lagarith and uncompressed], WAV, H.264, MPG2, AAC, etc). At the moment, every time I go to export to queue it locks up and hangs on the "Preparing data for export..." Media Encoder Launches and then it just freezes. I get "Problem Even Name: AppHangB1" over and over. Sometimes a full restart will fix this temporarily and sometimes it goes away for a long while. I managed to get a few sequences exported and then it just kept freezing on every PP CC restart.
Here are my system specs:
Premiere Pro CC (up to date)
Win 7 64bit (up to date)
i7 970
24GB Ram
NVIDIA 470GTX (driver up to date)
3 x 1.5TB internal
4TB internal
3TB internal
12TB RAID 5 via USB 3.0
USB 2.0 and 3.0 drives
FireWire audio device (M-AUDIO FireWire1814)... although, I am not using it for playback. It is connected.
Footage is from C100 H.264 .MTS, H.264.mov from 7D, and H.264 .MOV from iPhone.
All stock video plugins with a few third party audio plugs.
This problem happens with and without third party plugs, but it happens that this project uses them.
I have chatted with Adobe help twice about the matter and nothing has come of it. Log out, log in = same. Restart = same (sometimes), create new user account = same, and so on. The only thing I haven't done is completely re-install premiere, which seems a bit overkill. One of the reps said he would get back to me in a few days after he watched the issue via screen share. Never heard back.
I get the sense that this has something to do with PProHeadless.exe not launching or not running properly. When the crash happens on a fresh restart of PP CC 2014 PProHeadless is not running. I can start PProHeadless and it will send sequence to media encoder. When I try to export another sequence from the same project it crashes and I see another instance of PProHeadless launched.
Also, once the projects are exported to Media Encoder, I can encode them to any format with no problem. The problem is getting the sequences there!
Is there anything that I am overlooking here?
Thanks for the help!Hi
Premiere pro cc 2014 8.0.1 (21) build
Encoder CC 2014 8.0.1.48
I use CC for Teams so it updates all the time.
Again when I tried to use it today by letting premiere open it by sending an output into Queue it crashed both Encoder and Premiere.
In order to shut down Encoder and Premiere I had to go into Task Manager and "End Process Tree" on everything adobe I could find because just ending Encoder did not work it would not close. I remembered that years ago when Premiere would crash we had to end a photoshop process. I found photoshop open even though it was not "alive" on my task bar. I had used it yesterday but had closed it. I also had to close dynamiclinkmanager.exe *32 as well as one of the three Adobe CDF Helper.exe*32. They popped back on but Encode closed and then I got a message that Premiere needed to close and did when I clicked the button to let it close.
After all this I re-opened Encoder by itself and checked the Preferences finding that Import Sequences Natively option was again checked.
By the way for me, "Launch AME manually, then drag the sequence from PPro's Project panel to AME's Queue (or to a preset in the Preset Browser). That uses a different code path than the File>Export>Media workflow." won't work most of the time because I do live events of panel interviews that may run 2 or more hours. I need to break them down to chapters for the web
Also I know this isn't part of this problem but I and many others would still love dynamiclink to work to Encore because the DVD is not dead yet. The current work path is a drag.
Looks like some programers and engineers have some work to do.
Thanks
Dennis
My computer:
Self built PC windows 7 Professional 64 bit Build 7601 SP 1 I use auto update so it is up to date.
ASUS P6x58D Premium Motherboard
Intel (R) Core i7 930 @ 2.80 Ghz
Installed Memory 12 GB
NVIDIA GeForce 9500 GT
NVIDIA GeForce GTX 580
2 Apple Monitors and a HP full HD Monitor
With a BlackMagic Intensity Pro Capture Card -
Adobe Premiere Pro CC 2014 Will Not Open But other App like Lightroom will..
Hello,
Can someone please help with with this problem!?
I have just purchased Adobe Creative Student Cloud (the full set) and my Adobe Premiere Pro CC 2014 won't open when clicked on... however other App like Lightroom, indesign etc will... Can some explain why this is and help me load it up so i can start editing!
Thank you,
Georgeif you failed to reset the preferences, do it manually - Adobe Premiere Pro Help | Preferences
also, make sure your graphics card drivers are up-to-date. -
Premiere Pro CC 2014 won't open "because it is not responding".
When trying to open Premiere Pro CC 2014 it won't open and I get the message "You can't open the application "Adobe Premiere Pro CC 2014" because it is not responding.
I've done my updates, uninstalled it, reinstalled it. Even did a clean re-install of the Yosemite OS but nothing. It opens up fine on my laptop.
I'm on an iMac 27, late 2009.
2.66 GHz Intel Core i5
16GB RAM
ATI Radeon HD 4850 512 MB
Really need this to work asap.
Thanks.
/CarlA variety of issues can cause PPRO to crash on launch. Here are some of them:
a problem with the Preferences, or some other pref-related file in the Profile-<USERNAME> bin.
the graphics driver
having an integrated graphics chip as well as a graphics card. Disabling the integrated chip often fixes this.
having Nvidia CUDA drivers installed on a system with an AMD card
third-party plug-ins
a problem with the cache files.
a problem with the project file (if you're loading a project...)
folders that Premiere writes to being set to read-only
the user not having administrator rights
a conflict/incompatibility with some OS setting
a problem on the licensing/authentication side.
The fact that you've done a fresh installation of 10.10 eliminates some of those possibilities.
After a crash on launch, does a dialog box eventually come up prompting you to submit a crash report to either Adobe or Apple? If so, please click "information" or the like to access the crash log and copy/paste the report here. -
Premiere Pro CC 2014 Startup Crash "Quit Unexpectedly"
This morning, I take a look at Creative Cloud and there was 2 updates called "Adobe Premiere Pro CC 2014" and "Adobe Photoshop CC 2014". So, I figured, "Sure. Why not?" I updated them. So far, Photoshop still works. After Effects works too. But when I open Premiere Pro CC 2014, I get the pop-up screen, loading stuff and it just quit unexpectedly. I cleaned all of the Adobe products with the Cleaner Tool, uninstalled it, reinstalled it, opened it and it still happens. This is where it stops loading every time and quits. Also, love the artwork.
After that, it quits unexpectedly. Here is an image of that error.
I'm using a MacBook Pro. I don't know what to do. I really need help, guys.Solution:
My graphics card did not supported the "Mercury Playback Engine GPU Acceleration (Open CL)". You can change it into "Mercury Playback Engine Software Only" in your Project Settings.
But this is in the wrong place in my opinion. Why not in "Edit/Preferences"? I could've changed it by myself but I did not find the menu.
Thanks Michaela from the Adobe Support Chat! -
Premiere Pro CC 2014 with NVIDIA system freezes (Win7x64)
It appears after perhaps the last update Premiere Pro CC 2014 started freezing during editing. It appears to happen mostly with 4K material and using the Ultra key and alpha blending but may also occur with 4K titles. The sequences are 23.976 1080p, with mixed footage from the Sony A7S (50 Mbps XAVC-S/H.264) and GH4 (4K 100 Mbps H.264). There are also frequent crashes with GPUFoundation.dll (Mercury + CUDA). No freezing with software only rendering. I tried a variety of drivers when using a Quadro 5000 with no change in freeze behavior. I tried a new GTX 770 (clean driver install) and the freeze behavior and GPUFoundation.dll crashes are the same, however now even the mouse freezes. With the Quadro 5000, the entire Windows GUI would freeze (become inactive), however the mouse would still move. Thus, it appears there are issues with both NVidia drivers and Premiere Pro CUDA code path on Windows (app errors shouldn't be able to lock up the entire GUI). GPU Meter shows low GPU and GPU memory utilization during the freezes. The freezes typically occur when switching between clips during playback or scrubbing (more often with fast scrubbing). As a developer, it feels like some kind of semaphore lock / race condition, since during the freezes CPU, GPU, and memory utilization are very low. Additional hardware info: 2010 MacPro 12-Core, 24GB RAM running Win7x64 (with latest updates). Side note: PPro used to hang in memory on exit, but stopped after a recent Microsoft forced update (PPro now crashes sometimes on exit but no longer hangs in memory (used to have to kill it after exiting every time)). Has this been reported before? (A7S XAVC & GH4 4K footage is relatively new)
This crash occurred when dragging Black Video with Noise and other effects on top of alpha composited layers (+3 layers). CUDA turned the rendered area black, so I switched to OpenCL. This crash happened a few minutes later. While this would appear to be an Nvidia driver error (OpenCL), perhaps the developers can investigate. The system is very stable except when doing complex operations in PPro (and only PPro crashes). A tried and true Quadro 5000 crashed in the same way (totally different hardware and drivers).
The full debug info wouldn't post, edited shorter:
Application Specific Signatures:
Graphics hardware encountered an error and was reset: 0x0000001f
Process: Adobe Premiere Pro CC 2014 [380]
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.1 (8.0.1)
Code Type: X86-64 (Native)
Parent Process: launchd [191]
Responsible: Adobe Premiere Pro CC 2014 [380]
User ID: 501
Date/Time: 2014-10-01 03:13:25.803 -0700
OS Version: Mac OS X 10.9.5 (13F34)
Report Version: 11
Anonymous UUID: 3E030FD4-F38F-857C-3EB9-85D10E36AB49
Crashed Thread: 11 Dispatch queue: opencl_runtime
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
abort() called
Application Specific Signatures:
Graphics hardware encountered an error and was reset: 0x0000001f
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff8bcbfa1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8bcbed18 mach_msg + 64
2 com.apple.CoreFoundation 0x00007fff8bb10f15 __CFRunLoopServiceMachPort + 181
3 com.apple.CoreFoundation 0x00007fff8bb10539 __CFRunLoopRun + 1161
4 com.apple.CoreFoundation 0x00007fff8bb0fe75 CFRunLoopRunSpecific + 309
5 com.apple.HIToolbox 0x00007fff8d375a0d RunCurrentEventLoopInMode + 226
6 com.apple.HIToolbox 0x00007fff8d3757b7 ReceiveNextEventCommon + 479
7 com.apple.HIToolbox 0x00007fff8d3755bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
8 com.apple.AppKit 0x00007fff86c7424e _DPSNextEvent + 1434
9 com.apple.AppKit 0x00007fff86c7389b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
10 com.apple.AppKit 0x00007fff86c6799c -[NSApplication run] + 553
11 com.adobe.Frontend.framework 0x00000001000ca38d FE::MacApplication::RunSelf() + 45
12 com.adobe.Frontend.framework 0x000000010004898a FE::Application::Run(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 4058
13 com.adobe.Frontend.framework 0x00000001000cbc44 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
14 com.adobe.Frontend.framework 0x00000001000d2e25 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
15 com.adobe.AdobePremierePro 0x00000001000018ac main + 508
16 com.adobe.AdobePremierePro 0x00000001000016a4 start + 52
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff8bcc4662 kevent64 + 10
1 libdispatch.dylib 0x00007fff8a0c2421 _dispatch_mgr_invoke + 239
2 libdispatch.dylib 0x00007fff8a0c2136 _dispatch_mgr_thread + 52
Thread 2:
0 libsystem_kernel.dylib 0x00007fff8bcc464a kevent + 10
1 com.adobe.dvatransport.framework 0x0000000100e294fc boost::asio::detail::kqueue_reactor::run(bool, boost::asio::detail::op_queue<boost::asio::detail::task_io_service_operation>&) + 236
2 com.adobe.dvatransport.framework 0x0000000100e291a7 boost::asio::detail::task_io_service::do_run_one(boost::asio::detail::scoped_lock<boost:: asio::detail::posix_mutex>&, boost::asio::detail::task_io_service_thread_info&, boost::system::error_code const&) + 375
3 com.adobe.dvatransport.framework 0x0000000100e28d18 boost::asio::detail::task_io_service::run(boost::system::error_code&) + 552
4 com.adobe.dvatransport.framework 0x0000000100e18157 SkyConnectionEnv::MainLoop() + 167
5 com.adobe.dvatransport.framework 0x0000000100e17c09 SkyConnectionEnv::StaticThreadFunc(SkyConnectionEnv*) + 9
6 com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
7 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
8 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
9 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
Thread 3:
0 libsystem_kernel.dylib 0x00007fff8bcc3716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8c0d0c3b _pthread_cond_wait + 727
2 com.adobe.dvacore.framework 0x000000010036a0ab boost::asio::detail::task_io_service::do_run_one(boost::asio::detail::scoped_lock<boost:: asio::detail::posix_mutex>&, boost::asio::detail::task_io_service_thread_info&, boost::system::error_code const&) + 139
3 com.adobe.dvacore.framework 0x0000000100369e18 boost::asio::detail::task_io_service::run(boost::system::error_code&) + 552
4 com.adobe.dvacore.framework 0x0000000100369bda boost::asio::detail::posix_thread::func<boost::asio::detail::resolver_service_base::work_ io_service_runner>::run() + 42
5 com.adobe.dvatransport.framework 0x0000000100e29bb3 boost_asio_detail_posix_thread_function + 19
6 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
7 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
8 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
Thread 4:
0 libsystem_kernel.dylib 0x00007fff8bcc3716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8c0d0c3b _pthread_cond_wait + 727
2 com.apple.CoreServices.CarbonCore 0x00007fff824bc800 TSWaitOnCondition + 108
3 com.apple.CoreServices.CarbonCore 0x00007fff824bc9ff TSWaitOnConditionTimedRelative + 172
4 com.apple.CoreServices.CarbonCore 0x00007fff8248d145 MPWaitOnQueue + 192
5 com.adobe.dvacore.framework 0x00000001003a359d dvacore::threads::ThreadSafeDelayQueue::PopWithTimeout(std::auto_ptr<dvacore::threads::Al locatedFunctionT<boost::function<void ()> > >&, int) + 141
6 com.adobe.dvacore.framework 0x00000001003a1500 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 160
7 com.adobe.dvacore.framework 0x00000001003919ac boost::function0<void>::operator()() const + 28
8 com.adobe.dvacore.framework 0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
9 com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
10 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
11 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
12 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
Thread 5:
0 libsystem_kernel.dylib 0x00007fff8bcc3716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8c0d0c3b _pthread_cond_wait + 727
2 com.adobe.GPUFoundation.framework 0x000000010941b8d6 void boost::condition_variable_any::wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&) + 70
3 com.adobe.GPUFoundation.framework 0x0000000109419705 GF::Device::AcquireExclusiveAccess() + 117
4 com.adobe.PlayerMediaCore.framework 0x0000000129518684 AdobePlayer::PlayerDisplay::UpdateWindow() + 372
5 com.adobe.PlayerMediaCore.framework 0x000000012952b2a5 AdobePlayer::PlayerMain::OnUpdate() + 21
6 com.adobe.PlayerMediaCore.framework 0x0000000129530501 PrPlayModule<AdobePlayer::PlayerMain>::PlayEntry(int, pmStdParms*, void*, void*) + 241
7 com.adobe.PlayerMediaCore.framework 0x0000000129530390 xPlayEntry + 16
8 com.adobe.PlayerHost.framework 0x00000001057238c4 ML::CallPlayerModuleGuarded(int (*)(int, pmStdParms*, void*, void*), int, pmStdParms*, void*, void*, int*, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 276
9 com.adobe.PlayerHost.framework 0x0000000105721669 ML::PlayerModule::CallPlugin(int, void*, void*) + 153
10 com.adobe.PlayerHost.framework 0x0000000105745c36 ML::VideoPlayer::CallPlayModuleSelector_Update() + 86
11 com.adobe.PlayerHost.framework 0x000000010573421d ML::VideoPlayer::ForceDisplayRedraw(ML::PlayerOutputQuality) + 205
12 com.adobe.PlayerHost.framework 0x0000000105728a34 ML::PlayModuleThreadQueue::ExecuteDeferredCall(ASL::ObjectPtr<ML::DeferredCallBase, ASL::AtomicValue>) + 340
13 com.adobe.PlayerHost.framework 0x0000000105727935 ML::PlayModuleThreadQueue::ServiceQueue() + 293
14 com.adobe.dvacore.framework 0x00000001003a159e dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 318
15 com.adobe.dvacore.framework 0x00000001003919ac boost::function0<void>::operator()() const + 28
16 com.adobe.dvacore.framework 0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
17 com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
18 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
19 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
20 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
Thread 6:
0 libsystem_kernel.dylib 0x00007fff8bcc3716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff8c0d0c77 _pthread_cond_wait + 787
2 com.apple.CoreServices.CarbonCore 0x00007fff824bc9e7 TSWaitOnConditionTimedRelative + 148
3 com.apple.CoreServices.CarbonCore 0x00007fff8248d145 MPWaitOnQueue + 192
4 com.adobe.dvacore.framework 0x00000001003a359d dvacore::threads::ThreadSafeDelayQueue::PopWithTimeout(std::auto_ptr<dvacore::threads::Al locatedFunctionT<boost::function<void ()> > >&, int) + 141
5 com.adobe.dvacore.framework 0x00000001003a1500 dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 160
6 com.adobe.dvacore.framework 0x00000001003919ac boost::function0<void>::operator()() const + 28
7 com.adobe.dvacore.framework 0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
8 com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
9 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
10 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
11 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
Thread 7:
0 libsystem_kernel.dylib 0x00007fff8bcbfa1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8bcbed18 mach_msg + 64
2 libcuda_334.01.03_mercury.dylib 0x00000001223f85a2 cuosEventWait + 210
3 libcuda_334.01.03_mercury.dylib 0x000000012233e922 intHandlerMain + 114
4 libcuda_334.01.03_mercury.dylib 0x00000001223f9479 cuosPosixThreadStartFunc(void*) + 41
5 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
6 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
7 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
Thread 8:
0 libsystem_kernel.dylib 0x00007fff8bcbfa1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8bcbed18 mach_msg + 64
2 libclh.dylib 0x000000011ae0fe19 0x11a800000 + 6356505
3 libclh.dylib 0x000000011a8c5df2 0x11a800000 + 810482
4 libclh.dylib 0x000000011ae10c69 0x11a800000 + 6360169
5 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
6 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
7 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
Thread 9:
0 libsystem_kernel.dylib 0x00007fff8bcbfa1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8bcbed18 mach_msg + 64
2 libclh.dylib 0x000000011ae0fe19 0x11a800000 + 6356505
3 libclh.dylib 0x000000011a8c5df2 0x11a800000 + 810482
4 libclh.dylib 0x000000011ae10c69 0x11a800000 + 6360169
5 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
6 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
7 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
Thread 10:
0 libsystem_kernel.dylib 0x00007fff8bcbfa1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8bcbed18 mach_msg + 64
2 libclh.dylib 0x000000011ae0fe19 0x11a800000 + 6356505
3 libclh.dylib 0x000000011a8c5df2 0x11a800000 + 810482
4 libclh.dylib 0x000000011ae10c69 0x11a800000 + 6360169
5 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
6 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
7 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
Thread 11 Crashed:: Dispatch queue: opencl_runtime
0 libsystem_kernel.dylib 0x00007fff8bcc3866 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff8c0cf35c pthread_kill + 92
2 libsystem_c.dylib 0x00007fff8c131bba __abort + 145
3 libsystem_c.dylib 0x00007fff8c131b29 abort + 140
4 libGPUSupportMercury.dylib 0x00007fff89db41ca gpusKillClient + 111
5 libGPUSupportMercury.dylib 0x00007fff89db4b51 gpusQueueSubmitDataBuffers + 155
6 libclh.dylib 0x000000011a90ee26 0x11a800000 + 1109542
7 libclh.dylib 0x000000011a8b104a 0x11a800000 + 725066
8 libclh.dylib 0x000000011a8b10a1 0x11a800000 + 725153
9 libclh.dylib 0x000000011a8b4394 0x11a800000 + 738196
10 libclh.dylib 0x000000011a910425 clhCtxSynchronize + 21
11 com.nvidia.web.GeForceGLDriverWeb 0x00001234402e627d gldFinishQueue + 234
12 com.apple.opencl 0x00007fff87917abe 0x7fff87911000 + 27326
13 com.apple.opencl 0x00007fff87931123 0x7fff87911000 + 131363
14 com.apple.opencl 0x00007fff8793414a 0x7fff87911000 + 143690
15 libdispatch.dylib 0x00007fff8a0c028d _dispatch_client_callout + 8
16 libdispatch.dylib 0x00007fff8a0c6a18 _dispatch_barrier_sync_f_slow + 460
17 com.apple.opencl 0x00007fff87933faa 0x7fff87911000 + 143274
18 com.apple.opencl 0x00007fff8792a202 clEnqueueMapBuffer + 631
19 com.adobe.RendererGPU.framework 0x0000000111714245 GF::ScopedRecordedHostMemory::Map() const + 133
20 com.adobe.RendererGPU.framework 0x00000001117685ea RendererGPU::PointwiseFilterHostNode::ApplyConcatenatedPointwiseFilters(ASL::InterfaceRef <MF::IVideoFrame, MF::IVideoFrame> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame> const&, boost::shared_ptr<RenderResults> const&, std::vector<RendererGPU::PointwiseFilter, std::allocator<RendererGPU::PointwiseFilter> > const&) + 826
21 com.adobe.RendererGPU.framework 0x0000000111767daf RendererGPU::PointwiseFilterHostNode::Process(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&) + 831
22 com.adobe.RendererGPU.framework 0x000000011171d2b8 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 1448
23 com.adobe.RendererGPU.framework 0x00000001117ad03c RenderNodeBase::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 76
24 com.adobe.RendererGPU.framework 0x000000011171d094 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 900
25 com.adobe.RendererGPU.framework 0x00000001117ad03c RenderNodeBase::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 76
26 com.adobe.RendererGPU.framework 0x000000011171d094 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 900
27 com.adobe.RendererGPU.framework 0x00000001117ad03c RenderNodeBase::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 76
28 com.adobe.RendererGPU.framework 0x000000011171d094 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 900
29 com.adobe.RendererGPU.framework 0x00000001117194d5 RendererGPU::CompositorNode::Process(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&) + 1413
30 com.adobe.RendererGPU.framework 0x000000011171d2b8 RendererGPU::FilterNode::ProcessFrameOnDevice(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&) + 1448
31 com.adobe.RendererGPU.framework 0x000000011170f36f RendererGPU::(anonymous namespace)::RendererGPU::ProduceFrame(ASL::InterfaceRef<IRenderNode, IRenderNode> const&, RenderParams const&, boost::shared_ptr<RenderResults> const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, std::string*, ASL::ParamRect<int>) + 1279
32 com.adobe.PlayerMediaCore.framework 0x0000000129535bf0 AdobePlayer::RenderRequest::ProduceFrame(ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, RenderParams const&, std::string*, ASL::ParamRect<int>) + 96
33 com.adobe.PlayerMediaCore.framework 0x000000012951cefd AdobePlayer::PlayerDisplay::PresentRenderRequestImpl(boost::shared_ptr<AdobePlayer::Rende rRequest> const&) + 1901
34 com.adobe.PlayerMediaCore.framework 0x00000001295204db AdobePlayer::PlayerDisplay::PresentLastCompletedRenderRequestImpl() + 267
35 com.adobe.dvacore.framework 0x00000001003a159e dvacore::threads::(anonymous namespace)::ThreadedWorkQueue::WorkerMain(boost::shared_ptr<dvacore::threads::ThreadSafeD elayQueue> const&, boost::shared_ptr<dvacore::threads::Gate> const&) + 318
36 com.adobe.dvacore.framework 0x00000001003919ac boost::function0<void>::operator()() const + 28
37 com.adobe.dvacore.framework 0x000000010039e473 dvacore::threads::(anonymous namespace)::LaunchThread(std::string const&, boost::function0<void> const&, dvacore::threads::ThreadPriority, boost::function<void ()> const&, boost::function<void ()> const&) + 115
38 com.adobe.boost_threads.framework 0x0000000100294dba thread_proxy + 186
39 libsystem_pthread.dylib 0x00007fff8c0ce899 _pthread_body + 138
40 libsystem_pthread.dylib 0x00007fff8c0ce72a _pthread_start + 137
41 libsystem_pthread.dylib 0x00007fff8c0d2fc9 thread_start + 13
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 319
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: 56776
thread_create: 1
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=679.6M resident=223.0M(33%) swapped_out_or_unallocated=456.6M(67%)
Writable regions: Total=19.5G written=15.6G(80%) resident=14.2G(73%) swapped_out=3.0G(16%) unallocated=5.3G(27%)
REGION TYPE VIRTUAL
=========== =======
ATS (font support) 32.0M
ATS (font support) (reserved) 8K reserved VM address space (unallocated)
CG backing stores 23.8M
CG image 584K
CG raster data 48K
CG shared images 204K
CoreImage 8K
Foundation 4K
IOKit 78.3M
IOKit (reserved) 268K reserved VM address space (unallocated)
Image IO 1032K
Kernel Alloc Once 8K
MALLOC 1.5G
MALLOC (admin) 32K
MALLOC_LARGE (reserved) 512K reserved VM address space (unallocated)
Memory Tag 241 128K
Memory Tag 242 12K
Memory Tag 249 192K
Memory Tag 251 24K
OpenCL 1.0G
OpenGL GLSL 1664K
STACK GUARD 56.8M
Stack 113.7M
VM_ALLOCATE 52.6G
VM_ALLOCATE (reserved) 30.4M reserved VM address space (unallocated)
__DATA 71.6M
__IMAGE 528K
__LINKEDIT 225.7M
__NV_CUDA 456K
__TEXT 453.8M
__UNICODE 544K
mapped file 84.0M
shared memory 68K
=========== =======
TOTAL 56.3G
TOTAL, minus reserved VM space 56.3G
Model: MacPro5,1, BootROM MP51.007F.B03, 12 processors, 6-Core Intel Xeon, 2.93 GHz, 24 GB, SMC 1.39f11
Graphics: NVIDIA GeForce GTX 770, NVIDIA GeForce GTX 770, PCIe, 2048 MB
Memory Module: DIMM 1, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 2, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 3, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 5, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 6, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 7, 4 GB, DDR3 ECC, 1333 MHz, 0x857F, 0x463732353155363446393333334700000000
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 770, Display Controller, Slot-1
PCI Card: pci1095,3132, SATA Controller, Slot-2
PCI Card: NVIDIA GeForce GTX 770, NVDA,Parent, Slot-1
PCI Card: pci1b73,1100, USB eXtensible Host Controller, Slot-4
Serial ATA Device: HL-DT-ST DVD-RW GH61N
Serial ATA Device: WDC WD1001FALS-41Y6A0, 1 TB
Serial ATA Device: OWC Mercury Extreme Pro SSD, 240.06 GB
Serial ATA Device: OWC Mercury Extreme Pro SSD, 240.06 GB
Serial ATA Device: WDC WD4001FAEX-00MJRA0, 4 TB
USB Device: Scarlett 2i2 USB
USB Device: Keyboard Hub
USB Device: USB-PS/2 Optical Mouse
USB Device: Apple Keyboard
USB Device: My Passport 0741
USB Device: My Passport 0820
USB Device: USB3.0 Media Reader
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Logitech RumblePad 2 USB
USB Device: Mobile Keys 49
FireWire Device: built-in_hub, Up to 800 Mb/sec
Thunderbolt Bus:
Maybe you are looking for
-
2 months ago my ipod was stolen for a plummbing men that come to my home, i want to make the report, but i dont have anything to find my serail number, I tried itunes, but didnt find a link that had lead me to my seral number, the old boxes is gone,
-
How is an object created in a workflow ?
Hello, When i create a task and assign an organizational business object to it along with a method. When the workflow is activated then it will call this method, but who will create the object and who will fill up the initial attributes of the object
-
It works with youtube, but not my model railroader site. I have added the website to the exceptions list and contacted their administrator. Their administrator says firefox must be blocking it.
-
User exit in the transport proccess by stms
Hello everyone, I need to do some "abaps" in the event of transporting objects from one enviroment to an other (dev to qa to prod). I know i can make an enhancment in the standard transaction STMS cause i'm in ecc6 version. But, as a programmer, i'm
-
Hi ya, Does HTTP 1.1 run over HTTP 1.0? Can one application running HTTP 1.0 COMMUNICATE with the other running HTTP 1.1? Or am I mistaken?