Premiere Pro CS5.5 crashing while opening any project but new
Premiere Pro keeps crashing when I attempt to open any previously saved project.
If media to a project is not linked, it will open the box to relink, but selecting "link" or "offline" both lead to a crash once the workspace attempts to load.
I am on a 3.4 Ghz Intel Core i7 iMac. AMD Radeon HD 6970M 1024 MB with Lion 10.7.4. I updated my PP and Media Encoder.
I have the Master Suite CS5.5, but mostly live in PS, AI and DW. I searched through the discussions and found a number of posts regarding crashes, but they all seem to have different problems/solutions. The issue is now over my head. Any suggestions?
Also, I read on a few discussions that it is recommended to run PP on a seperate machine because when a problem arises it is easier to discover its cause. If I don't have the means to do this, are there any tips for it to run seamlessly?
Below is the script from problem report.
Thanks for your time,
George
[Please don't post full crash reports in the forum. It makes scrolling through a thread very unwieldy. If an Adobe staff member wants to see one, you can PM the report separately.]
The first thing that I would do is to look over this FAQ Entry, and then post the details - the more the better. http://forums.adobe.com/thread/961741?tstart=0
If your Projects are behaving as the OP's were, and the media is in a similar place, be sure to list everything.
Good luck,
Hunt
Similar Messages
-
Premiere Pro CC crashing after opening autosave project
PP CC crashes quite often.
Working since weeks on a 60-minute-documentary with mixed footage (4K XAVC / Canon XF / XDcam HD 422).
Because of the many crashes (5-10 per day) I´ve have to reopen / restore many times autosave-projects.
Not a good idea: because most projects are corrupt.
At least when I try to integrate the whole project into a new one.
Importing just the sequence into a new project works fine - but I also need my sorted BINS (structure, files, etc.)
What can I do?
new Mac Pro 8core
64GB
10.9.5
PP CC
Thanks for your help,
ReinhardHi Reinhard,
Reinhard Kungel wrote:
PP CC crashes quite often.
Sorry to hear that. Please check out this doc: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later)
You also might try the following:
Sign out from Creative Cloud, restart Premiere Pro, then sign in
Update any GPU drivers
Trash preferences
Delete media cache
Delete preview files
Remove plug-ins
If you have AMD GPUs, make sure CUDA is not installed
Repair permissions
In Sequence Settings > Video Previews, change the codec to one that matches your footage
Disconnect any third party hardware
If you have a CUDA GPU, ensure that the Mercury Playback Engine is set to CUDA, not OpenCL
Disable App Nap
Reboot
Report back if anything here worked for you.
Thanks,
Kevin -
Premiere Pro CS5 crashes while editing 4.5K-RED-Material
Hi there,
I'm editing 4.5K-material with Premiere Pro CS5. After a couple of minutes (mostly after watching sequences longer then 10 seconds) the program crashes. Windows 7 tells me that "ImporterREDServer.exe" doesn't work anymore and then Premiere freezes. I doubt that it is a performance problem, because with CS4 and regular 4K-RED-material I haven't had any problems on the same PC. I deinstalled CS5 several times (with Cleanupscript and everything) and re-installed it, but the problem remained the same.
I would really appreciate some help or any idea what the problem could be. Thanks in advance!
Daniel
My system:
i7 860 @ 2.8 GHz
8 GB RAM
Windows 7Well, well. After many tests with other platforms we came to the conclusion that it was not Premiere Pro that caused problems but the material itself. This is some kind of a worst case scenerio. In the process of copying the data onto hdds some frames within the data got damaged and causes Premiere to crash. Since the data on both discs is corrupt differently we now try to rebuild as many files as possible. Yet there will be clips that can't be saved. Anyhow. There will be a film and that's the most important thing.
Thanks again for your help everybody
Daniel -
Premiere Pro CC crashes in opening a project file
I am using Premiere Pro CC since 1.5 years now. No big problems so far but now suddenly a strange one in opening a project file.
Several other project files open up as usual, but the last one I've been working on, suddenly crashes in the middle of loading the media files. An error message like this appears:
"Premiere Pro has encountered an error. [c:\ppro772\releases\2013.10\shared\adobe\mediacore\mediafoundation\api\inc\ " (and the rest of the path I'm not able to see, it's cut.)
I have installed the latest version of the graphics driver today. I have installed Premiere Pro 2014 some time ago but didn't really use it yet. I already tried to open the project in 2014 with no success.
Now I just found out that I can open the project from the one-before-the-last autosave file! Thereafter I saved the project with a different name, but trying to re-open it resulted again in the same error!!
Any idea what the problem could be and what might help?BUt that's a different error.
I am getting this one aswell.
[c:\ppro772\releases\2013.10\shared\adobe\mediacore\mediafoundation\api\inc
Please fix it.
I really want my Premiere Pro to work :\ -
Premiere Pro CC Crashes upon opening a Project file
Get error: [/sirreel64/releases/2013.02/shared/adobe/MediaCore/MediaLayer/ImporterHost/Make/Mac/../. ./Src/Audio/AudioWaveform.cpp-173]
Then it crashes.
I have tried: Re-Installing, clearing the Cache, changing my region to USA (Computer), turning off various features, changing scratch disk
I'm using a 2012 iMac, Mavericks, up to date.
Have been using CS5, 5.5, & 6 on this system just fine.
My system:
3.1 GHz Intel Core i5
16GB 1333 MHz RAM
AMD Radeon HD 6970M 1024 MB
I'm a professional editor and very tech saavy, save the 'did you turn it off and on again' responses please.
Thread 22 Crashed:: Dispatch queue: com.apple.root.low-priority
0 libsystem_kernel.dylib 0x00007fff8c456a52 __semwait_signal_nocancel + 10
1 libsystem_c.dylib 0x00007fff8f9b4a7c nanosleep$NOCANCEL + 189
2 libsystem_c.dylib 0x00007fff8f9de5fe usleep$NOCANCEL + 54
3 libsystem_c.dylib 0x00007fff8fa0abc4 abort + 135
4 com.adobe.Frontend.framework 0x000000010006728a FE::ApplicationErrorManager::ThrowError(dvacore::config::ErrorLevel, char const*, unsigned int, int, bool, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&) const + 202
5 com.adobe.dvacore.framework 0x00000001002a1962 dvacore::config::ThrowError(dvacore::config::ErrorLevel, char const*, unsigned int, int, bool, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&) + 226
6 com.adobe.ImporterHost.framework 0x0000000104df6879 ML::AudioWaveform::SetSingleChannel(int) + 185
7 com.adobe.Backend.framework 0x0000000101c41a3d BE::Media::SyncToMediaInfo(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 7069
8 com.adobe.Backend.framework 0x0000000101c48880 BE::Media::SetMediaInfo(ASL::InterfaceRef<BE::IMediaInfo, BE::IMediaInfo>, dvamediatypes::FrameRate const&, bool) + 4288
9 com.adobe.Backend.framework 0x0000000101c4734a BE::Media::RelinkMediaInfo() + 1466
10 com.adobe.Backend.framework 0x0000000101c468ea non-virtual thunk to BE::Media::CheckMediaInfoRelink(bool) + 58
11 com.adobe.Backend.framework 0x0000000101c4fb86 BE::(anonymous namespace)::HandleOneRelinkRequest() + 326
12 com.adobe.dvacore.framework 0x0000000100326642 dvacore::threads::(anonymous namespace)::SubExecutorImpl::CallFunctionWithExceptionHandler(boost::function<void ()> const&) + 66
13 com.adobe.dvacore.framework 0x00000001003250a8 dvacore::threads::(anonymous namespace)::SubExecutorImpl::OnThreadExecute(boost::shared_ptr<dvacore::threads::(anonymo us namespace)::SubExecutorImpl> const&) + 232
14 com.adobe.dvacore.framework 0x00000001003383d4 dvacore::threads::WrapExecuteTopLevelFunction(void*) + 68
15 libdispatch.dylib 0x00007fff91cef2ad _dispatch_client_callout + 8
16 libdispatch.dylib 0x00007fff91cf109e _dispatch_root_queue_drain + 326
17 libdispatch.dylib 0x00007fff91cf2193 _dispatch_worker_thread2 + 40
18 libsystem_pthread.dylib 0x00007fff8c43bef8 _pthread_wqthread + 314
19 libsystem_pthread.dylib 0x00007fff8c43efb9 start_wqthread + 13BUt that's a different error.
I am getting this one aswell.
[c:\ppro772\releases\2013.10\shared\adobe\mediacore\mediafoundation\api\inc
Please fix it.
I really want my Premiere Pro to work :\ -
Premiere Pro CS5 crash when adjusting audio gain
Premiere Pro CS5 crash when adjusting audio gain
The same on another workstations.
Have any idea?Hi Dennis,
I just had a go and can reproduce the problem straight away too.
Created a new project then a new XDCAM EX 1080p25 sequence. Imported a short Sony PMW-350 clip. Dragging it straight to the timeline and then setting audio gain is OK (Source channel mapping preferences set to mono).
However, if I Modify - Audio Channels and then set track format as stereo or mono as stereo and then drag the clip to the timeline and right click - gain, Premiere crashes about 1/2 to 1 second after the audio gain dialogue box appears. Error log below if it's useful.
Asus Rampage III extreme
Intel i7 980x @ 3.33GHz
24Gb ram
Windows 7 64 bit
Using onboard sound - Realtek HD 6.0.1.6037
Incidentally, I tried with both the default Windows 7 audio drivers and then the Realtek HD drivers installed (I'd previously forgotten to install the Realtek driver when I built the PC)
Log Name: Application
Source: Application Error
Date: 12/08/2010 14:28:51
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Faulting application name: Adobe Premiere Pro.exe, version: 5.0.1.0, time stamp: 0x4bf119d2
Faulting module name: MSVCR90.dll, version: 9.0.30729.4926, time stamp: 0x4a1750b0
Exception code: 0xc0000005
Fault offset: 0x000000000001dfcd
Faulting process id: 0x16ec
Faulting application start time: 0x01cb3a21ad8357e4
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CS5\Adobe Premiere Pro.exe
Faulting module path: C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_08e1a05ba 83fe554\MSVCR90.dll
Report Id: 8b5dda37-a615-11df-8de4-20cf3011131b
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-08-12T13:28:51.000000000Z" />
<EventRecordID>2401</EventRecordID>
<Channel>Application</Channel>
<Computer></Computer>
<Security />
</System>
<EventData>
<Data>Adobe Premiere Pro.exe</Data>
<Data>5.0.1.0</Data>
<Data>4bf119d2</Data>
<Data>MSVCR90.dll</Data>
<Data>9.0.30729.4926</Data>
<Data>4a1750b0</Data>
<Data>c0000005</Data>
<Data>000000000001dfcd</Data>
<Data>16ec</Data>
<Data>01cb3a21ad8357e4</Data>
<Data>C:\Program Files\Adobe\Adobe Premiere Pro CS5\Adobe Premiere Pro.exe</Data>
<Data>C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_08e 1a05ba83fe554\MSVCR90.dll</Data>
<Data>8b5dda37-a615-11df-8de4-20cf3011131b</Data>
</EventData>
</Event> -
Premiere Pro CS5 crashes when clock wipe transition is applied
Hi,
I applied a transition "CLOCK WIPE" and when i change any parameter within the transistion then Premiere Pro CS5 crashes.
What I have tested is that only happens when the mercury playback engine is turned on.Adobe Feature Request/Bug Report Form
-
Logic Pro X crash while opening project
Hello all,
Using Logic since 9 came out. Saw that X was released so I figured I'd do it right...new SSD OS X drive, clean install of Mountain Lion 10.8, maxed out my 12 core Mac Pro with 64 GB ram, downloaded the new Logic Pro X, re-installed my Native Instruments Komplete 8 bundle. I've been using it trouble-free now for about a week, and loving the update. Until now.
One of my projects crashed and now it won't re-open.
I tried re-booting.
I trashed my preference files and restarted.
I can open Logic Pro, and other project files OK. I opened the Audio Units Manager and disabled ALL plugins, Quit Logic and restarted. Still crashes when opening this project file.
If it's not the plugins, and Logic is working fine otherwise, it must be something to do with a particular audio file within the bin. So I moved the Audio Files folder to my desktop and Skipped the locate files option. Still crashes.
All software is up to date. Any suggestions? Here's the most recent crash report, after disabling all plugins and moving the audio files:
Process: Logic Pro X [1264]
Path: /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X
Identifier: com.apple.logic10
Version: 10.0.1 (2911.42)
Build Info: MALogic-2911042000000000~1
App Item ID: 634148309
App External ID: 15875534
Code Type: X86-64 (Native)
Parent Process: launchd [145]
User ID: 501
Date/Time: 2013-07-29 01:34:04.730 -0700
OS Version: Mac OS X 10.8.4 (12E55)
Report Version: 10
Interval Since Last Report: 19612 sec
Crashes Since Last Report: 20
Per-App Interval Since Last Report: 1933 sec
Per-App Crashes Since Last Report: 9
Anonymous UUID: 440AE3AB-E35C-970B-F4A5-4A31E5AC7F78
Crashed Thread: 26 SeqTimer
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000001055b9000
VM Regions Near 0x1055b9000:
__LINKEDIT 00000001055b0000-00000001055b9000 [ 36K] r--/rwx SM=COW /Applications/Logic Pro X.app/Contents/Frameworks/MAGFFoundation.framework/Versions/A/MAGFFoundation
--> MALLOC guard page 00000001055b9000-00000001055ba000 [ 4K] ---/rwx SM=NUL
MALLOC metadata 00000001055ba000-00000001055cf000 [ 84K] rw-/rwx SM=PRV
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff96e3e78e mach_wait_until + 10
1 com.apple.CoreServices.CarbonCore 0x00007fff8f20a226 MPDelayUntil + 12
2 com.apple.CoreServices.CarbonCore 0x00007fff8f2193cf Delay + 70
3 com.apple.logic10 0x00000001013c3de4 0x100f9a000 + 4365796
4 com.apple.logic10 0x0000000100fa0abd 0x100f9a000 + 27325
5 com.apple.logic10 0x0000000101112861 0x100f9a000 + 1542241
6 com.apple.logic10 0x0000000101162135 0x100f9a000 + 1868085
7 com.apple.logic10 0x000000010145118c 0x100f9a000 + 4944268
8 com.apple.logic10 0x000000010141eafc 0x100f9a000 + 4737788
9 com.apple.logic10 0x00000001014233cb 0x100f9a000 + 4756427
10 com.apple.logic10 0x000000010142350d 0x100f9a000 + 4756749
11 com.apple.AppKit 0x00007fff9039f348 -[NSDocument _initWithContentsOfURL:ofType:error:] + 135
12 com.apple.AppKit 0x00007fff9039eff4 -[NSDocument initWithContentsOfURL:ofType:error:] + 262
13 com.apple.AppKit 0x00007fff907c7765 -[NSDocumentController makeDocumentWithContentsOfURL:ofType:error:] + 332
14 com.apple.logic10 0x0000000101533d5e 0x100f9a000 + 5872990
15 com.apple.AppKit 0x00007fff907d21f3 -[NSDocumentController(NSDeprecated) openDocumentWithContentsOfURL:display:error:] + 824
16 com.apple.logic10 0x0000000101446afa 0x100f9a000 + 4901626
17 com.apple.Foundation 0x00007fff9360a9cf -[NSBlockOperation main] + 124
18 com.apple.Foundation 0x00007fff935e0926 -[__NSOperationInternal start] + 684
19 com.apple.Foundation 0x00007fff935e80f1 __block_global_6 + 129
20 libdispatch.dylib 0x00007fff902a3f01 _dispatch_call_block_and_release + 15
21 libdispatch.dylib 0x00007fff902a00b6 _dispatch_client_callout + 8
22 libdispatch.dylib 0x00007fff902a50c8 _dispatch_main_queue_callback_4CF + 275
23 com.apple.CoreFoundation 0x00007fff9339bb4c __CFRunLoopRun + 1644
24 com.apple.CoreFoundation 0x00007fff9339b0e2 CFRunLoopRunSpecific + 290
25 com.apple.HIToolbox 0x00007fff99599eb4 RunCurrentEventLoopInMode + 209
26 com.apple.HIToolbox 0x00007fff99599c52 ReceiveNextEventCommon + 356
27 com.apple.HIToolbox 0x00007fff99599ae3 BlockUntilNextEventMatchingListInMode + 62
28 com.apple.AppKit 0x00007fff90486533 _DPSNextEvent + 685
29 com.apple.AppKit 0x00007fff90485df2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
30 com.apple.AppKit 0x00007fff9047d1a3 -[NSApplication run] + 517
31 com.apple.AppKit 0x00007fff90421bd6 NSApplicationMain + 869
32 com.apple.logic10 0x000000010141da69 0x100f9a000 + 4733545
33 com.apple.logic10 0x0000000100f9cc34 0x100f9a000 + 11316
Thread 1:
0 libsystem_kernel.dylib 0x00007fff96e406d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff921f5f4c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff921f5d13 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff921e01d1 start_wqthread + 13
Thread 2:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff96e40d16 kevent + 10
1 libdispatch.dylib 0x00007fff902a2dea _dispatch_mgr_invoke + 883
2 libdispatch.dylib 0x00007fff902a29ee _dispatch_mgr_thread + 54
Thread 3:
0 libsystem_kernel.dylib 0x00007fff96e406d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff921f5f4c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff921f5d13 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff921e01d1 start_wqthread + 13
Thread 4:: com.apple.NSURLConnectionLoader
0 libsystem_kernel.dylib 0x00007fff96e3e686 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff96e3dc42 mach_msg + 70
2 com.apple.CoreFoundation 0x00007fff93396233 __CFRunLoopServiceMachPort + 195
3 com.apple.CoreFoundation 0x00007fff9339b916 __CFRunLoopRun + 1078
4 com.apple.CoreFoundation 0x00007fff9339b0e2 CFRunLoopRunSpecific + 290
5 com.apple.Foundation 0x00007fff93589546 +[NSURLConnection(Loader) _resourceLoadLoop:] + 356
6 com.apple.Foundation 0x00007fff935e7562 __NSThread__main__ + 1345
7 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
8 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 5:
0 libsystem_kernel.dylib 0x00007fff96e406d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff921f5f4c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff921f5d13 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff921e01d1 start_wqthread + 13
Thread 6:
0 libsystem_kernel.dylib 0x00007fff96e406d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff921f5f4c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff921f5d13 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff921e01d1 start_wqthread + 13
Thread 7:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x00007fff96e40322 __select + 10
1 com.apple.CoreFoundation 0x00007fff933daf46 __CFSocketManager + 1302
2 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
3 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 8:
0 libsystem_kernel.dylib 0x00007fff96e3e686 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff96e3dc42 mach_msg + 70
2 com.apple.CoreFoundation 0x00007fff93396233 __CFRunLoopServiceMachPort + 195
3 com.apple.CoreFoundation 0x00007fff9339b916 __CFRunLoopRun + 1078
4 com.apple.CoreFoundation 0x00007fff9339b0e2 CFRunLoopRunSpecific + 290
5 com.apple.Foundation 0x00007fff935ec7ee -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 268
6 com.apple.Foundation 0x00007fff935ec69b -[NSRunLoop(NSRunLoop) runUntilDate:] + 78
7 com.apple.logic10 0x0000000101177d1f 0x100f9a000 + 1957151
8 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
9 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 9:
0 libsystem_kernel.dylib 0x00007fff96e3e686 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff96e3dc42 mach_msg + 70
2 com.apple.audio.midi.CoreMIDI 0x00000001029f3970 XServerMachPort::ReceiveMessage(int&, void*, int&) + 96
3 com.apple.audio.midi.CoreMIDI 0x0000000102a0fb23 MIDIProcess::RunMIDIInThread() + 243
4 com.apple.audio.midi.CoreMIDI 0x00000001029f4c2c XThread::RunHelper(void*) + 10
5 com.apple.audio.midi.CoreMIDI 0x00000001029f480f CAPThread::Entry(CAPThread*) + 175
6 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
7 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 10:: ExtendedAudioFileScheduler::WorkerThreadProc
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAFiles 0x0000000104590c23 ExtendedAudioFileScheduler::WorkerThreadProc() + 115
3 com.apple.music.apps.MAFiles 0x00000001045908d9 ExtendedAudioFileScheduler::WorkerThreadProc(void*) + 9
4 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
5 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 11:: ExtendedAudioFileScheduler::WorkerThreadProc
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAFiles 0x0000000104590c23 ExtendedAudioFileScheduler::WorkerThreadProc() + 115
3 com.apple.music.apps.MAFiles 0x00000001045908d9 ExtendedAudioFileScheduler::WorkerThreadProc(void*) + 9
4 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
5 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 12:: com.apple.audio.IOThread.client
0 libsystem_kernel.dylib 0x00007fff96e3e686 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff96e3dc42 mach_msg + 70
2 com.apple.audio.CoreAudio 0x00007fff94155c1c HALB_MachPort::SendMessageWithReply(unsigned int, unsigned int, unsigned int, unsigned int, mach_msg_header_t*, bool, unsigned int) + 98
3 com.apple.audio.CoreAudio 0x00007fff94155baa HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 42
4 com.apple.audio.CoreAudio 0x00007fff94153fe9 HALC_ProxyIOContext::IOWorkLoop() + 1161
5 com.apple.audio.CoreAudio 0x00007fff94153acf HALC_ProxyIOContext::IOThreadEntry(void*) + 83
6 com.apple.audio.CoreAudio 0x00007fff941539a7 HALB_IOThread::Entry(void*) + 75
7 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
8 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 13:: ProcessThread1/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467cc53 MD::CallProcessThread1(void*) + 563
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 14:: ProcessThread2/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467cf01 MD::CallProcessThread2(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 15:: ProcessThread3/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467d191 MD::CallProcessThread3(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 16:: ProcessThread4/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467d421 MD::CallProcessThread4(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 17:: ProcessThread5/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467d6b1 MD::CallProcessThread5(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 18:: ProcessThread6/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467d941 MD::CallProcessThread6(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 19:: ProcessThread7/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467dbd1 MD::CallProcessThread7(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 20:: ProcessThread8/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467de61 MD::CallProcessThread8(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 21:: ProcessThread9/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467e0f2 MD::CallProcessThread9(void*) + 578
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 22:: ProcessThread10/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467e381 MD::CallProcessThread10(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 23:: ProcessThread11/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467e611 MD::CallProcessThread11(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 24:: ProcessThread15/1024
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x000000010467f051 MD::CallProcessThread15(void*) + 577
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 25:: FileIOThread
0 libsystem_kernel.dylib 0x00007fff96e400fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff921f7fe9 _pthread_cond_wait + 869
2 com.apple.music.apps.MAAudioEngine 0x0000000104698765 0x10466c000 + 182117
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 26 Crashed:: SeqTimer
0 com.apple.logic10 0x0000000101243260 0x100f9a000 + 2789984
1 com.apple.logic10 0x000000010124dffa 0x100f9a000 + 2834426
2 com.apple.logic10 0x000000010124bad7 0x100f9a000 + 2824919
3 com.apple.logic10 0x0000000101249ca7 0x100f9a000 + 2817191
4 com.apple.CoreServices.CarbonCore 0x00007fff8f219a43 TimerThread + 134
5 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
6 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 27:
0 libsystem_kernel.dylib 0x00007fff96e40322 __select + 10
1 com.apple.logic10 0x00000001017f6e64 0x100f9a000 + 8769124
2 com.apple.logic10 0x000000010140121d 0x100f9a000 + 4616733
3 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
4 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 28:
0 libsystem_kernel.dylib 0x00007fff96e406d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff921f5f4c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff921f5d13 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff921e01d1 start_wqthread + 13
Thread 29:: com.apple.appkit-heartbeat
0 libsystem_kernel.dylib 0x00007fff96e40386 __semwait_signal + 10
1 libsystem_c.dylib 0x00007fff9227d800 nanosleep + 163
2 libsystem_c.dylib 0x00007fff9227d717 usleep + 54
3 com.apple.AppKit 0x00007fff9066b838 -[NSUIHeartBeat _heartBeatThread:] + 543
4 com.apple.Foundation 0x00007fff935e7562 __NSThread__main__ + 1345
5 libsystem_c.dylib 0x00007fff921f37a2 _pthread_start + 327
6 libsystem_c.dylib 0x00007fff921e01e1 thread_start + 13
Thread 26 crashed with X86 Thread State (64-bit):
rax: 0x00000001055b8ff0 rbx: 0x000000000000fc80 rcx: 0x0000000000000800 rdx: 0x0000000000000000
rdi: 0x00000000ffffffff rsi: 0x000000000000fc80 rbp: 0x000000011a3c0c20 rsp: 0x000000011a3c0b40
r8: 0x3ffffffeffffffff r9: 0x0000000102099000 r10: 0x00000000000000e5 r11: 0x80000000000000f0
r12: 0x00007fac9436a000 r13: 0x0000000102099000 r14: 0x0000000109b4efa0 r15: 0x00007fac9e3cdb50
rip: 0x0000000101243260 rfl: 0x0000000000010287 cr2: 0x00000001055b9000Alcologic wrote:
Hello all,
One of my projects crashed and now it won't re-open.
I tried re-booting.
I trashed my preference files and restarted.
I can open Logic Pro, and other project files OK. I opened the Audio Units Manager and disabled ALL plugins, Quit Logic and restarted. Still crashes when opening this project file.
Hi, it looks like a Project file corruption from what you are writing.
Let's try one more thing before going any further!
We will disable the Audio Drivers:
Hold down Control immediately (NOT TOGETHER) after clicking Logic in your Dock.
A dialog will open :
Press "Don't".
Does the problematic project open? -
Premiere Pro CS5 crashing when exporting (only certain file types)
Hi
I have found that when I try and export media in Premiere Pro CS5, it often crashes during the export. It says
It's only certain file types. For instance, Vimeo HD seems okay but Vimeo SD always crashes mid-export. MPEG is okay too, but MPEG2-DVD always crashes.
Sometimes it says this: "Error Compiling Movie - Unknown Error" but doesn't throw me out of Premiere altogether.
Other times it crashes altogether and Windows gives me this error message: "Display driver NVIDIA Windows Kernel Mode Driver, Version 258.96 stopped responding and has successfully recovered". Premiere Pro then stops responding so I have to re-open it and start exporting again.
I have checked there are no gaps in my timeline and I have rendered the whole work area. Besides, I doubt it's anything that I'm doing wrong with the project itself because it's exporting fine in some formats.
I am also experiencing random crashes when editing too. Not that often, but occasionally it throws me out - and twice it has made the whole screen go crazy, with weird dotting across the screen (it's scary, it looks like the monitor itself has broken!).
Any help would be appreciated!
Nick
PS I have a pretty decent new PC - Dell Studio XPS, 8GB, 2x1TB drives, etc. Premiere itself is working great, except for these crashes.Some drivers do not work well in some systems... so go to nVidia and try a different (usually newer) driver for your card
These notes are for Encore, but they MAY also work in Premiere
Long File Names or odd characters Cause Crashing http://forums.adobe.com/thread/588273
And #4 Here http://forums.adobe.com/thread/666558?tstart=0
And This Message Thread http://forums.adobe.com/thread/665641?tstart=0 -
Premiere Pro CS5 crashing and not allowing updates
Hello,
I'm experiencing two problems with ProCS5.
First, while in pro, the program crashes when I click on a video clip in the Lib to view it in the monitor.
Second, I tried to update to the program hoping to correct the first issue, but the update returns the error "installation unsuccessful" for unknown reasons.
I am running:
Model Name: Mac Pro
Model Identifier: MacPro1,1
Processor Name: Dual-Core Intel Xeon
Processor Speed: 2.66 GHz
Number Of Processors: 2
Total Number Of Cores: 4
L2 Cache (per processor): 4 MB
Memory: 7 GB
Bus Speed: 1.33 GHz
I just installed a 1.5T hard drive for video editing and formatted as Mac OS Extended (Journaled).
I can view the videos directly from the hard drive and the play back is fine. I'm only having this problem in Premiere Pro CS5.
Any help will be greatly appreciated
Regards,
DS>just not Mpeg 4s
Read Bill Hunt on a file type as WRAPPER http://forums.adobe.com/thread/440037?tstart=0
What is a CODEC... a Primer http://forums.adobe.com/thread/546811?tstart=0
What CODEC is INSIDE that file? http://forums.adobe.com/thread/440037?tstart=0
Report back with the codec details of your file, use the programs below
For Mac http://mediainfo.massanti.com/
Once you know exactly what it is you are editing, report back with that information... and your project setting, and if there is a red line above the video in the timeline, which indicates a mismatch between video and project -
Premiere Pro CS5 crash on startup
Before I was having a problem with cs5 crashing, I uninstalled and reinstalled the master collection, then updated everything. Premiere Pro cs5 seemed to work fine, I was jumping in my seat with the new mercury engine and how fast it was compared to cs4, but now today I come back to find out its crashing again on startup
I have 5.0.2 installed
On the side note Photoshop (even with its latest update) crashes on type tool
Running latest OSX
Tried changing permissions, reinstalling, everything! For now I guess i'll have to use cs4hi.. DigitalRicky,
did you ever come to a solution for this?
I believe I am having the same or simular problem.
im on a mac .. 10.5.8 with enought disk spack.. about 50gb
have downloaded update for primiere.
two things are happening
1.freezes/stalls/doesn't respond on opening program.. I have to force quit it or on some occasions it just quits itself. this occurs on new and exsisiting projects.
2. on 3 occasions after i had fiddled around with deleting preferences, i have been able to edit .. however no unable to add footage as the second i trie to add footage to timeline it stalls/freezes/does not respond. then i have a world of hurt and can't re open.. back to problem 1.
what trouble shooting i have done..
1. uninstall/reinstall
2. run no other software etc.
3. Documents>Adobe>AdobeProductName (like Premiere Pro) Inside of this, there is a folder with a number (usually 4.0 for CS4). Take that to the trash and restart your application. -> this is where i can start old project but not a new one..
4. run disk utility on comp
5. re start comp etc
im not to sure on what else i can do ..
I would GREATLY appreciate any help.
thanks heaps!
Danielle -
Premiere pro cs5 crashing on start up
I have an imac i7 and i am a final cut pro user and i wanted to try adobe premiere pro cs5 before i bought well i installed it on my alumunium macbook (late 2008 model) which is and intel dual core 2 ghz processor and 4 gigs of ram and it runs perfectly fine no problems kinda like it, but when i install it on my imac i7 it runs for a little bit then crashes on start up. i even did a full system install of osx and it worked for a little and stopped and now just crashes everytime on start up, and its only premiere pro cuz i downloaded the master collection trial. and everything installed on my macbook is the exact same as installed on my imac i7. so i dont know what the heck is wrong uninstalled a million times, and i dont want to buy this software if i cant even get it to work on the main system i need it to work on. can any one help? here is a piece of the crash report.
Application Specific Information:
*** error for object 0x10daac200: incorrect checksum for freed object - object was probably modified after being freed.First, I am a PC-guy, and know almost zero about Macs, so take this with a handful of salt.
Similar issues in PC's can be caused by programs that incorrectly report their memory address usage to the OS, or programs that tell the OS they have released that memory address, but have, in fact, not done so.
Now, even if that is what is causing your issue, I have no clue how one could check on a Mac, but we have a lot of Mac-users around here, who can likely tell you that I am crazy and my comments do not apply to a Mac, or how to check.
Good luck,
Hunt -
Premiere Pro CS5 Crashing in Windows 7
Hello,
Recently I have been experiencing program crashes in Premiere Pro CS5. Everything works fine, until I try to import some media. It often imports fine, however when it comes to conforming, he whole program freezes and Windows Error Report comes up. This happens everytime. I thought that it could possibly be a problem with my computers hardware (as I had been running Premiere Pro on the bare minimum requirements). So I upgraded my Processor from a Dual Core 2.0Ghz to a Quad Core 2.5Ghz. I also doubled the RAM from 2GB to 4GB. Yet the same error still occurs. Has anybody else been experiencing the same problem, and are there any steps I can take to fix it?Welcome to the forum.
What are the full specs. of your Source Files, and what is the Sequence Preset?
Also, please tell us about your system's I/O, i.e. the HDD's, and especially things like defragmented free space. The more details, the better.
Last, are you running Win7-64 with but 4GB of RAM? That is just about enough to run Win7-64, and leave little, if any, for PrPro.
Good luck,
Hunt -
Premiere Pro CS5 Crashes on Startup on Mac
Hi,
I have installed Master Collection CS5 on a MacBook Pro (late 2009) Mac OSX 10.6..4 (4GB RAM) with all Apple updates applied as at 26.8.2010 , Photoshop & Illustrator work fine , Premiere Pro & Soundbooth CS5 repeatedly crash when starting up & have never worked since installing.
I have lodged this problem with Adobe Tech Support.
One typical error message is "/Scully64/shared/adobe/MediaCore/ASL/Foundation/Make/Mac/../..Src/Di r ectoryRegistry.cpp-283" on launching Premiere Pro Cs5r aniother might be " No client name has encountered an error" or "Premiere Pro has encountered an error"
I have uninstalled CS5 , used the CS5 Cleanup tool , reinstalled Master Collection CS5 (several times) the only existing Admin user account , repaired Mac hard drive Disk Permissions ( in Disk Utility) , & checked /repaired any Font errors/duplications all with no luck.
Does anyone have an answer ?
Thanks,
RickI don't recognize those error messages, but you should try installing the recent Premiere Pro update, which fixes several crashing problems.
When you have updated Premiere Pro CS5, let us know whether your problem is fixed.
See this page for details about the Premiere Pro CS5 (5.0.2) update:
http://bit.ly/djiyh4
Please report bugs that persist after the update here:
http://www.adobe.com/go/wish -
Crashes while opening specific project in Professional 2010
Hi,
I am keep on crashing my MS Project Professional while opening specific project, able to edit other projects without any issues .
event viewer gives following error message, not able to find pdb files to debug
Faulting application name: WINPROJ.EXE, version: 14.0.4751.1000, time stamp: 0x4b8e2648
Faulting module name: WINPROJ.EXE, version: 14.0.4751.1000, time stamp: 0x4b8e2648
Exception code: 0xc0000005
Fault offset: 0x0018e4a4
Faulting process id: 0xe44
Faulting application start time: 0x01d019598e0af28c
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office14\WINPROJ.EXE
Faulting module path: C:\Program Files (x86)\Microsoft Office\Office14\WINPROJ.EXE
Report Id: 03f5cf9b-854d-11e4-b02f-1c659dacae4b
any pointers to trace the issue
S.Venkata AppajiAppaji,
My guess is the file is corrupt. But first, let's make sure you have SP2 installed. It appears from the version number above that you do not. You can download SP2 at: http://support.microsoft.com/kb/2687457. I also recommend you install the June 2013 cumulative
update. You can get that at: http://support2.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2817385&kbln=en-us.
If after installing the updates you still cannot open the file, go to the MVP website at, http://project.mvps.org/faqs.htm and take a look at FAQ 43. Use method 4.
Hope this helps.
John
Maybe you are looking for
-
Hello, this is my first post. I just upgraded from the original 2006 17" Macbook Pro to a refurbished 13" Macbook Pro 2.53GHZ 4GB Ram (2009 model). I bought the MCE Tech Optibay and installed it (if you dont know anything about it, ask me, its amazin
-
Why is iTunes using 2gb of my ram?
I noticed that my computer was being really slow and sluggish, so I opened the activity monitor and I saw that iTunes was using 2gb of ram! I didn't have anything playing, downloading, etc. It was just open in the background. I'm running OSX 10.8.5.
-
Loading an object - best practice
i'm currenlty loading a collection of objects and trying to determine which is the best way to "load" the object. Should i be calling set functions on the object and specifying the values or should i simply call a load function on the object and pass
-
Ovi Suite 3.0.0.284 has stopped working on windows...
Hello, Since I bought the Nokia N8 and I'm trying to run the Ovi Suite I always get the message "Nokia Ovi Suite has stopped working" "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution
-
Why is my Airport so Weak?
I have Macbook with OS 10.7.4 I live in an apartment with several bedrooms and the wireless router is in the hall, maybe 5 meters from my laptop (in my bedroom). The wireless works, but very badly. I'm constantly moving my laptop around in my room to