FCP quits when DV deck turned on

Dear all,
Out of the blue, my FCP has begun to quit on me repeatedly. I think I have narrowed the circumstances down to it happening once I swtich on my DV deck (Sony M15 attached by Firewire).
The FCP/deck combination has worked fine for the 4 months I have had the deck but not now! I cannot think of anything I did just before the problem started except perhaps installing a Digital Heaven Plug-ins for a Grid overlay but I have since deleted that.
If anyone can help, I would be most grateful.
Cheers,
Hamish
iMac 2 Ghz intelduo Mac OS X (10.4.8)

I hate sound pedantic, but this is basic stuff.
Also found easily by searching the internet and these boards.
http://docs.info.apple.com/article.html?artnum=93385
http://www.ncmug.org/tips/repair_permissons.html
But the real issue is Rosetta and why you starting a project on Intel hardware without the proper software.
If you are not much into this project, you might want to start over with the correct application version

Similar Messages

FCP - Quits when using pen tool to enter nodes in the motion tab

Hi all.
I'm encountering a persistent problem with FCP unexpectedly quitting on both version 4.5HD and version 5. The problem occurs when I open a clip from the timeline in the viewer and access the motion tab to adjust the scale of a clip or the position of a clip with the pen tool. I can enter four nodes successfully with no problems, but if I then go back to the clip or open a new one, I can enter maybe three nodes maximum before they cease to register, then the beachball appears for half a second and FCP quits with the "unexpected" message.
This problem occurs across all machines whether I'm running FCP by itself or with other applications running in the background. I am using 10.4.6 on my laptop (iBook G4 with 1GB of RAM and FCP 4.5HD), 10.3.9 and FCP 4.5HD on an eMac, 10.4.6 and FCP Studio 5.0.4 on a G4 Tower ...
Has anyone experienced a similar problem, and does anyone have any thoughts on causes/fixes for it?
Thanks for reading.
L.
Either: iBook G4, eMac, G4 Tower, Mac-Mini, 20" Intel iMac Mac OS X (10.4.6)

Hi John,
Thanks. I figured it out so there’s no need.
Aloha,
Rick Doyle
[personal information removed... Mod - https://forums.adobe.com/docs/DOC-3731]
[This is an open forum, not Adobe support, please do not post personal information]
[If you are posting using email, please turn your 'sig file' function OFF for posting]

FCP quits when making round trip to motion

When I try to make to make the round trip with one or more clips to motion(using "sendto" and with "embed" ticked on), everything seems to work fine, but when I save the motion project and quit motion FCP just quits "unexpectedly".
When I then restart FCP, I can import the saved motion project, but as soon as I try to play it in the viewer, or I drop it in the timeline, FCP quits again...
Any advice ?
G5 Quad Mac OS X (10.4.7) decklink extreme

You'd be answering your own question.
The workflow for colorgrade has evolved over the last twenty or so years (in video) and over the last better part of a century in film as the final step, after everything was LOCKED. Its kind of why this application was first named "Final Touch".... well, it was sort of a clever reference to "Final Cut"... but... we know how that worked out.
It would be a bit misleading to conceptualize COLOR as a kind of really fancy 3-way, but the fact remains that as an external application, it creates all new media, independent in most ways from the original sources. We can understand that as an extension of the workflow from the days of linear tape-to-tape, when an entirely new, "Color-Correct" Master was created. Some flexibility can be built in to the return trip with the use of handles... but it can also turn into a whole other can'o'worms. Keyframed stuff can get out of sync.... etc.
jPo

FCP quits when exporting ref movie or self contained

This one has be pulling my hair out. When I try to export an hour long project, FCP quits about half way in. Doesn't seem to matter if it is a ref movie or self contained. I get the unexpectedly quit window. I have no idea how to fix this. It is extremely frustrating. Any ideas?
Best.
Tom

Don't use an XDCAM sequence setting. Mixing that format with ANY OTHER FORMAT causes issues. I have had 3 jobs in the last 2 weeks that were HDV and XDCAM, and when they were in their native timeline settings, with other footage and graphics mixed in, I had HORRID times exporting and outputting. The solution? Changing the sequence compressor to ProRes, and rendering again. Then the projects exported fine.
So my rule #1 when dealing with HDV or XDCAM, is to edit in a ProRes sequence...all the time. No matter what. Dealing with GOP native, when you add other things like stills or other footage, is cause for nightmare issues. That GOP format is just too whacky to deal with.
Shane

FCP quits when opening project

Hi all, I have been running FCP 5.1.1 for a while now, never had a problem. Been working on an on-going project that always took a few extra seconds to read and load. Well last night I digitized about 2 more hours of video to the project, did a few edits on the timeline and saved and closed. No problems that I could see. Now today when I go to open the project, I get the "Reading Project" box, and at 43%, FCP just closes, "FCP Quit Unexpectedly". I click "try again", same thing happens. Anybody have any ideas? Is there a limit to how much a project can handle? Thanks!

hi Joe
this is not uncommon behaviour if and when a sorce clip becoms corrupted.
if that is the case, what you can do is disconnect the media drive and then launch FCP. it should open up fine but all the media will be offline.
now you can reconnect the media drive and relink the media, but take care in this last step, relink the media in blocks, making a mental note of which clips you are reconnecting each time ... eventually you will get the error, which tells you that it is one of those last blaock of clips that has become corrupted.
when you discover the corrupt clip you can relink all the others and recapture the corrupted one from source.
hope that helps
Andy

FCP quits when importing pics

Doing a project with lots of yearbook pics, and about half the time FCP "unexpectedly quits" when importing these pics. They're regular jpegs, no noticeable pattern, so I now transfer pics to desktop and do it from there. Best way is to set all material in media as a few of you told me, but I'm too far into this project and it's almost done. Any ideas as to why FCP quits would be greatly appreciated.

Make sure all your jpegs are RGB and not CMYK.
rh

FCP quits when move within timeline

Hi everybody,
I am experiencing something unsual with a rather big project (1h20 mn right now) using many different imported clips and pictures.
When I move the cursor from the end to the begining of the timeline, I noticed that FCP will quit with a message telling me that it quits unexpectedly.
When it dies so, I trash preferences, but as soon as I do it again, I get the same problem.
Could it be because of the size of the project ? Am I going to fast from onepoint to the other ? or is it something else ?
There is plenty of room on the disk.
Thanks in advance
I am using FCP4.5

General stability problems sounds like...
How much RAM do you have installed? When you upgraded
to Tiger, did you perform a totally clean install, or
just run the "upgrade" install? (bad idea)...
Hi jerry...
RAM is 1 Go, Tiger installed from totally cleaned hard disk
Large numbers of edits in projects can result in
instability if there is not enough RAM to help out,
but if the install of Tiger wasn't performed as a
clean install, and reinstall of software, that too
can result in instability issues. Further, Tiger uses
more system resources than Panther or Jaguar, and
this might just push your RAM too hard running FCP
with many edit sequences and cause the crash...If you
have less than a gig of RAM I suspect this is or is
part of the problem.
Corrupt media can also cause this, so be sure that's
not the problem. Only way to tell is to temporarily
take it offline. and reconnect a few clips at a time
to see if there's a crash of some sort when you hit
the bad media. Also keep all media OFF your startup
disk. This results in problems as well. A firewire
drive should do the job for you if the media is on
your internal disk on the PB... it's a must really
too.
All clips originate from DVDs made up from shootage made by myself on my video camera.
I had them on external disk and imported them, one by one on the hard disk of my PWB for making of the project
Jerry

FCP quits without reason when i try to log clips

I have a brand new Mac Pro with a 2.66 Quad Core processor, 6 gb of ram, the latest OS (10.6.2) and i'm having trouble getting Final Cut Pro to work propperly. It runs very slowly every time i try to edit h.264, and when i try to log any clip, FCP quits without reason. My software is original, it is the Studio pro 2 (Final Cut Pro 6.0.6) Does anyones knows what is wrong or what could it be?

OK - it is possible that you do not have a fast enough Hard Drive Capture Scratch location to handle uncompressed capture. You may need to setup a RAID if you do not have that already. I saw that you have a Mac Pro, so you could set two or three drives up as a RAID if you want, or employ an external FW800 RAID.
If this isn't your problem, or if you already know this, than maybe you should either trash your "preferences", or look at un-checking "Abort capture on dropped frame" in the "General" tab of User Preferences.
I hope this is helpful Chikimi. -s

FCP 5 quits when opening a project file

Hello...hope someone can help.
I have a project file that gets past all the plugins (I don't have any extras) and then quits when it starts loading. Other project files load fine.
I trashed my preferences, restarted in safe boot and repaired permissions through the Disk Utility program. I moved my media to another folder...and it still does it for this one project file.
Any ideas?
Thanks..

try creating a new user on your computer. Open the project file under that new user. If it won't open, you have a corrupted project file. I hope you have a back-up!

FCP HD 4.5 quits when clicking Log and Capture window

I am running FCP 4.5 with a G4 dual 1.42 Ghz Tiger and everytime I click Log and capture FCP quits...I have uninstalled and reinstalled from my original disks and still no luck...have used FCP rescue...no luck.....
Really not having fun tonight...if there is any help out there I thank you in advance....
Sincerely
Kris

Welcome to the discussions, Kris.
Just to be sure, you did use the FCP Rescue for pre-rev5, right?
Next, what are you trying to capture from? Do you have anything else on the FW bus? An iSight camera can cause problems. I guess I should ask if you're trying to capture from FW.
Next, you re-installed your program, but FCP uses QuickTime to capture. Have you tried re-installing QuickTime? Use the procedure outlined in the top post in the discussions - the one about Camera Recognition - you may have a faulty install of QuickTime.
Post back,
Patrick

Mail unexpectedly quits when launching

My mail quits when I try to launch. Usually it gets to the point of connecting to my mail server, and then dies.
I have tried repairing permissions, disk repair, and tech tool. I have downloaded and reinstalled the combined update
Here is a snippet from the crash report
Date/Time: 2006-09-20 08:18:42.229 -0400
OS Version: 10.4.7 (Build 8J135)
Report Version: 4
Command: Mail
Path: /Applications/Mail.app/Contents/MacOS/Mail
Parent: WindowServer [176]
Version: 2.1 (752)
Build Version: 1
Project Name: MailViewer
Source Version: 7520000
PID: 238
Thread: 1
Exception: EXCBADACCESS (0x0001)
Codes: KERNINVALIDADDRESS (0x0001) at 0x448dbb48
ANy ideas?

Thanks for the suggestions.
I tried both. Deleting the pref file would not even let me launch MAIL
Turning off Junk Mail filtering did not help either.
I have run Tech Tool, repaired permissions again, and reinstalled cumulative update again.
If I leave the network connection unplugged, it will launch and quit randomly after a minute or two of struggling
ANy help would be greatly appreciated
Thread 1 Crashed:
0 ...apple.AddressBook.framework 0x94cadb88 c4_FormatB::Define(int, unsigned char const**) + 212
1 ...apple.AddressBook.framework 0x94cab234 c4_HandlerSeq::Prepare(unsigned char const**, bool) + 372
2 ...apple.AddressBook.framework 0x94cabf68 c4_FormatV::SetupAllSubviews() + 160
3 ...apple.AddressBook.framework 0x94cad660 c4_FormatV::Get(int, int&) + 44
4 ...apple.AddressBook.framework 0x94cad5d0 c4_Handler::GetBytes(int, c4_Bytes&, bool) + 44
5 ...apple.AddressBook.framework 0x94cad588 c4_Sequence::Get(int, int, c4_Bytes&) + 88
6 ...apple.AddressBook.framework 0x94cad4d8 c4_ViewRef::operator c4_View() const + 76
7 ...apple.AddressBook.framework 0x94cac924 c4_Storage::Description(char const*) + 96
8 ...apple.AddressBook.framework 0x94cae084 c4_Storage::GetAs(char const*) + 100
9 ...apple.AddressBook.framework 0x94caf2ec cacheViews + 240
10 ...apple.AddressBook.framework 0x94ca9674 -[ABAddressBook nts_OpenContactManagerWithMode:cacheSchema:] + 452
11 ...apple.AddressBook.framework 0x94ca81d0 -[ABAddressBook nts_InitDefaultContactManager] + 1052
12 ...apple.AddressBook.framework 0x94ca7d0c +[ABAddressBook nts_SharedAddressBook] + 76
13 ...apple.AddressBook.framework 0x94ca7c40 +[ABAddressBook nts_CreateSharedAddressBook] + 76
14 ...apple.AddressBook.framework 0x94ca7b64 +[ABAddressBook sharedAddressBook] + 80
15 com.apple.MessageFramework 0x9a00aef4 -[MailAddressManager loadAddressBookSynchronously] + 44
16 libobjc.A.dylib 0x90a431f4 objc_msgSendv + 180
17 com.apple.Foundation 0x9293bc88 -[NSInvocation invoke] + 944
18 com.apple.MessageFramework 0x99ff6800 -[MonitoredInvocation invoke] + 144
19 com.apple.MessageFramework 0x99fffe80 -[InvocationQueue _drainQueue] + 416
20 com.apple.Foundation 0x92940194 forkThreadForFunction + 108
21 libSystem.B.dylib 0x9002bc28 pthreadbody + 96
And then
Thread 1 crashed with PPC Thread State 64:
srr0: 0x0000000094cadb88 srr1: 0x000000000000d030 vrsave: 0x0000000000000000
cr: 0x44044244 xer: 0x0000000000000006 lr: 0x0000000094cadb7c ctr: 0x0000000090003e50
r0: 0x0000000094cadb7c r1: 0x00000000f0181b60 r2: 0x00000000401dcb48 r3: 0x000000000465a1f0
r4: 0x00000000004d1660 r5: 0x000000000000006e r6: 0x0000000000000000 r7: 0x0000000000000001
r8: 0x0000000004702b48 r9: 0x0000000004705000 r10: 0x0000000004700b44 r11: 0x0000000044044242
r12: 0x0000000090003858 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
r16: 0x0000000000000000 r17: 0x0000000000000000 r18: 0x0000000000000000 r19: 0x0000000000000000
r20: 0x0000000000000000 r21: 0x00000000f0182090 r22: 0x0000000000000007 r23: 0x00000000004f7630
r24: 0x00000000f0182080 r25: 0x00000000f0181f50 r26: 0x00000000004f78b0 r27: 0x00000000f01820b0
r28: 0x000000000461c770 r29: 0x000000000465a1f0 r30: 0x00000000100772d2 r31: 0x0000000094cab0d0

CRM 2011: when auditing is turned off, why do existing Audit records lose "New Value"?

Not sure if this is by design (if so, would love to know why!) or if this is a bug. Let's say I have auditing turned on for Accounts. I change the phone number in the Main Phone field from 555-1111 to 555-5555, and an audit record is
created showing the Old Value (555-1111) and New Value (555-5555). Great. Now I turn off auditing. The system goes back to the audit record that had previously been created, and modifies it so that it shows the Old Value (555-1111),
and inserts an icon into the New Value field indicating auditing was turned off. The tool tip for that icon states "Auditing was stopped and restarted. The new values for the fields that changed during this period cannot be identified or recorded."
First of all (minor picky issue) auditing hasn't been turned back on yet, despite what the tool tip says (says the same thing whether or not auditing is turned back on). But the real problem is
why the existing audit record's New Value would be removed... why would that happen?!? We're talking about a historical update. It really did change, and the system knew what it changed from/to, so why would the system remove that new value
from the audit record? Logically I would expect that any changes made
while auditing is off would not be logged, and that once auditing is turned back on, Old/New values would correspond to whatever was/is in the system at the time that any new audit record is created, so there may be a disconnect between an older audit
record and a new one (old record's New Value not matching the new record's Old Value, because changes were made while auditing was off). And it's quite apparent when auditing is turned off, because an audit record is created stating "Auditing Disabled".
Any ideas if there's a logical reason why it would do this, or if this is really a bug that Microsoft needs to fix? We have a client with a business need to periodically turn off auditing while integration updates run between CRM and another system
(otherwise hundreds of thousands of unnecessary audit records would be created). But if they're going to lose audit data every time they disable auditing, the auditing is worthless.

We wouldn't ever temporarily turn auditing off on purpose... it's happening when we import managed solutions. We have vendors with managed solutions that contain system entities such as Contacts. When importing their solution, it momentarily
turns auditing off on those entities. The only evidence of this is audit records indicating "Entity Audit Stopped", and of course the loss of all the most recent "new value" on all audit records. The interesting (?) parts of this are:
1. When importing the managed solution, the recommended option to keep all existing customizations is selected. I would think this would include the audit settings on the entity, but apparently not (sort of... see #2).
2. As soon as the managed solution is imported, in addition to creating an "Entity Audit Stopped" audit record on relevant entities and wiping out new values, it apparently turns auditing back on, yet there's no record of this (in customizations, the entity
still (or once again) indicates auditing is enabled; but on records for that entity, there is no "Entity Audit Enabled" record.
So, now it's on to working with the vendors, to dig into their managed solutions and see if there's a way to prevent this!

I purchased my fcp but it's doesn't open all I have is the FCp quit unexpectedly what can I do to fix this

I purchased my fcp but it's doesn't open all I have is the FCp quit unexpectedly what can I do to fix this

yes...a future release...for all of us pro editors here
on a side note - DH, i don't know you personally, but you've been a wealth of information over the years. I'll miss you when Apple finally kills off Final Cut PRO for good. Thanks for all the good times

Get error message that skype has problem loading when computer is turned on the first time every day. this started when the latest firefox v6.0 was downloaded.

get error message that skype has problem loading when computer is turned on the first time every day. this started when the latest firefox v6.0 was downloaded.

''mbratlie [[#question-1055011|said]]''
<blockquote>
It was working fine and I had no problems, and then one day I tried opening a window and it froze. When I tried quiting the program my whole window went black. The x to the close the window doesn't work. The only option I have in my tool bar is Firefox and nothing happens when I try to quit firefox. Every time I try to shut down my computer Firefox prevents it. I haven't updated Firefox yet, so it's an older program, but only by a month or two. What's going on and how do I fix it?
</blockquote>
This is the first time it's ever happened. I downloaded the new operating system for Firefox but I can't install it until the Firefox currently running on my laptop quits, which it won't.

Mail quits when I hit reply

Recently moved to a new job, and have my personal mac as my main workstation, connected to a standard monitor, keyboard and mouse. I have a very similar setup at my home office.
A few days ago, I started getting an unusual error whereby mail would unexpectedly quit when I tried to reply to a message. This repros every time, but doesn't repro when I connect to my home network (via Airport).
I tried searching using some key things out of the error report--it looks maybe like a kernel failure/inaccessible memory address problem (he said quite tentatively)? But so far have found nothing that works. I thought it was a driver issue, so I tried new keyboard/mouse and none at all (still repros). I thought it might be a corrupted mail prefs issue, so deleted com.apple.mail.plist but it still happens.
I thought it might be a problem with my accounts, so I deleted each mail account (there are several, a mixture of POP and IMAP, google and .mac) and re-added each account.
Now I'm getting a new, additional problem. The original bug still repros, but now all my messages show up in beige in the main list window as if they're junk (they were just all getting sent to junk, until I turned off the send-to-junk mail-folder feature). If I mark them not junk, they turn black; when I quit out of mail and open it again, they're beige again.
Everything updated in terms of my sys software. Any ideas? IS there a way to just uninstall/reinstall mail, or do you have to do a whole new system install?
Here is the first bit of the failure report--let me know if you need more. Thanks in advance!
code:
Date/Time: 2006-09-20 17:11:47.889 +0100
OS Version: 10.4.7 (Build 8J135)
Report Version: 4
Command: Mail
Path: /Applications/Mail.app/Contents/MacOS/Mail
Parent: WindowServer [57]
Version: 2.1 (752)
Build Version: 1
Project Name: MailViewer
Source Version: 7520000
PID: 326
Thread: 9
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000000
PB 15" 1.67 Mac OS X (10.4.7)
PB 15" 1.67 Mac OS X (10.4.7)

Thanks David- Still a problem, though. I did the following:
-Repaired disk using disk utility from OSX install disk
-Installed combined update
-Updated further using system update
-Repaired permissions
-Followed your directions in other threads for re-setting the junk mail filter (which seems to have helped my other problem).
I am still having the issue. No problem when I'm using my laptop at home, crashes when I try and reply to a message only when I'm connected to my office lan.
Here's the latest crash report:
Date/Time: 2006-10-03 12:11:40.725 +0100
OS Version: 10.4.8 (Build 8L127)
Report Version: 4
Command: Mail
Path: /Applications/Mail.app/Contents/MacOS/Mail
Parent: WindowServer [57]
Version: 2.1 (752)
Build Version: 1
Project Name: MailViewer
Source Version: 7520000
PID: 279
Thread: 11
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000000
Thread 0:
0 libSystem.B.dylib 0x9000ab48 machmsgtrap + 8
1 libSystem.B.dylib 0x9000aa9c mach_msg + 60
2 com.apple.CoreFoundation 0x907dcb78 __CFRunLoopRun + 832
3 com.apple.CoreFoundation 0x907dc47c CFRunLoopRunSpecific + 268
4 com.apple.HIToolbox 0x93203740 RunCurrentEventLoopInMode + 264
5 com.apple.HIToolbox 0x93202dd4 ReceiveNextEventCommon + 380
6 com.apple.HIToolbox 0x93202c40 BlockUntilNextEventMatchingListInMode + 96
7 com.apple.AppKit 0x936e5ae4 _DPSNextEvent + 384
8 com.apple.AppKit 0x936e57a8 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 116
9 com.apple.AppKit 0x936e1cec -[NSApplication run] + 472
10 com.apple.AppKit 0x937d287c NSApplicationMain + 452
11 com.apple.mail 0x000871d8 0x1000 + 549336
12 com.apple.mail 0x00087080 0x1000 + 548992
Thread 1:
0 libSystem.B.dylib 0x90054ae8 semaphoretimedwait_signaltrap + 8
1 libSystem.B.dylib 0x90054944 pthreadcondtimedwait + 676
2 com.apple.Foundation 0x929dc5a0 FCONDITION_WAITTIMEOUT + 144
3 com.apple.Foundation 0x929dc4bc -[NSConditionLock lockWhenCondition:beforeDate:] + 128
4 com.apple.MessageFramework 0x99fe9d90 -[InvocationQueue _drainQueue] + 176
5 com.apple.Foundation 0x9295d194 forkThreadForFunction + 108
6 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 2:
0 libSystem.B.dylib 0x9000ab48 machmsgtrap + 8
1 libSystem.B.dylib 0x9000aa9c mach_msg + 60
2 com.apple.CoreFoundation 0x907dcb78 __CFRunLoopRun + 832
3 com.apple.CoreFoundation 0x907dc47c CFRunLoopRunSpecific + 268
4 com.apple.Foundation 0x9296c164 -[NSRunLoop runMode:beforeDate:] + 172
5 com.apple.Foundation 0x9296c09c -[NSRunLoop run] + 76
6 com.apple.MessageFramework 0x99fee198 +[_NSSocket _runIOThread] + 92
7 com.apple.Foundation 0x9295d194 forkThreadForFunction + 108
8 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 3:
0 libSystem.B.dylib 0x9001f08c select + 12
1 com.apple.CoreFoundation 0x907ef40c __CFSocketManager + 472
2 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 4:
0 libSystem.B.dylib 0x90054ae8 semaphoretimedwait_signaltrap + 8
1 libSystem.B.dylib 0x90054944 pthreadcondtimedwait + 676
2 com.apple.Foundation 0x929dc5a0 FCONDITION_WAITTIMEOUT + 144
3 com.apple.Foundation 0x929dc4bc -[NSConditionLock lockWhenCondition:beforeDate:] + 128
4 com.apple.MessageFramework 0x99fe9d90 -[InvocationQueue _drainQueue] + 176
5 com.apple.Foundation 0x9295d194 forkThreadForFunction + 108
6 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 5:
0 libSystem.B.dylib 0x90054ae8 semaphoretimedwait_signaltrap + 8
1 libSystem.B.dylib 0x90054944 pthreadcondtimedwait + 676
2 com.apple.Foundation 0x929dc5a0 FCONDITION_WAITTIMEOUT + 144
3 com.apple.Foundation 0x929dc4bc -[NSConditionLock lockWhenCondition:beforeDate:] + 128
4 com.apple.MessageFramework 0x99fe9d90 -[InvocationQueue _drainQueue] + 176
5 com.apple.Foundation 0x9295d194 forkThreadForFunction + 108
6 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 6:
0 libSystem.B.dylib 0x90054ae8 semaphoretimedwait_signaltrap + 8
1 libSystem.B.dylib 0x90071168 pthreadcond_timedwait_relativenp + 556
2 ...apple.AddressBook.framework 0x94d29cac -[ABRemoteImageLoader workLoop] + 132
3 com.apple.Foundation 0x9295d194 forkThreadForFunction + 108
4 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 7:
0 libSystem.B.dylib 0x9000ab48 machmsgtrap + 8
1 libSystem.B.dylib 0x9000aa9c mach_msg + 60
2 com.apple.CoreFoundation 0x907dcb78 __CFRunLoopRun + 832
3 com.apple.CoreFoundation 0x907dc47c CFRunLoopRunSpecific + 268
4 com.apple.Foundation 0x9298469c +[NSURLConnection(NSURLConnectionInternal) _resourceLoadLoop:] + 264
5 com.apple.Foundation 0x9295d194 forkThreadForFunction + 108
6 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 8:
0 libSystem.B.dylib 0x9000ab48 machmsgtrap + 8
1 libSystem.B.dylib 0x9000aa9c mach_msg + 60
2 com.apple.CoreFoundation 0x907dcb78 __CFRunLoopRun + 832
3 com.apple.CoreFoundation 0x907dc47c CFRunLoopRunSpecific + 268
4 com.apple.Foundation 0x929857dc +[NSURLCache _diskCacheSyncLoop:] + 152
5 com.apple.Foundation 0x9295d194 forkThreadForFunction + 108
6 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 9:
0 libSystem.B.dylib 0x9000ab48 machmsgtrap + 8
1 libSystem.B.dylib 0x9000aa9c mach_msg + 60
2 com.apple.CoreFoundation 0x907dcb78 __CFRunLoopRun + 832
3 com.apple.CoreFoundation 0x907dc47c CFRunLoopRunSpecific + 268
4 com.apple.Foundation 0x9296c164 -[NSRunLoop runMode:beforeDate:] + 172
5 com.apple.Foundation 0x9296c09c -[NSRunLoop run] + 76
6 com.apple.WebKit 0x95687f70 +[WebFileDatabase _syncLoop:] + 176
7 com.apple.Foundation 0x9295d194 forkThreadForFunction + 108
8 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 10:
0 libSystem.B.dylib 0x90054ae8 semaphoretimedwait_signaltrap + 8
1 libSystem.B.dylib 0x90054944 pthreadcondtimedwait + 676
2 com.apple.Foundation 0x929dc5a0 FCONDITION_WAITTIMEOUT + 144
3 com.apple.Foundation 0x929dc4bc -[NSConditionLock lockWhenCondition:beforeDate:] + 128
4 com.apple.MessageFramework 0x99fe9d90 -[InvocationQueue _drainQueue] + 176
5 com.apple.Foundation 0x9295d194 forkThreadForFunction + 108
6 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 11 Crashed:
0 com.apple.CoreFoundation 0x9082ef70 CFReadStreamGetError + 56
1 com.apple.ISSupport 0x988e96f8 -[ISS_DAVRequest(Private) _readStreamEvent:] + 952
2 com.apple.CoreFoundation 0x90829eb4 _CFStreamSignalEventSynch + 332
3 com.apple.CoreFoundation 0x907dd4cc __CFRunLoopDoSources0 + 384
4 com.apple.CoreFoundation 0x907dc9fc __CFRunLoopRun + 452
5 com.apple.CoreFoundation 0x907dc47c CFRunLoopRunSpecific + 268
6 com.apple.ISSupport 0x98914ee4 +[ISS_AYOperation _dispatchNextOperationInQueue] + 716
7 com.apple.ISSupport 0x98915030 +[ISS_AYOperation _workerThread] + 200
8 com.apple.Foundation 0x9295d194 forkThreadForFunction + 108
9 libSystem.B.dylib 0x9002b508 pthreadbody + 96
Thread 11 crashed with PPC Thread State 64:
srr0: 0x000000009082ef70 srr1: 0x000000000200f030 vrsave: 0x0000000000000000
cr: 0x24000222 xer: 0x0000000000000004 lr: 0x000000009082ef40 ctr: 0x000000009082ef38
r0: 0x0000000000402210 r1: 0x00000000f059a1b0 r2: 0x00000000a07ba274 r3: 0x00000000f059a250
r4: 0x0000000000000000 r5: 0x0000000000000008 r6: 0x00000000ffffffff r7: 0x0000000000000001
r8: 0x0000000000000000 r9: 0x000000000000009c r10: 0x00000000988e80b4 r11: 0x00000000a88df8dc
r12: 0x000000009082ef38 r13: 0x0000000000000000 r14: 0x0000000000000001 r15: 0x0000000000000000
r16: 0x0000000000000001 r17: 0x0000000000000000 r18: 0x0000000000000000 r19: 0x0000000000000000
r20: 0x0000000000000000 r21: 0x0000000000000000 r22: 0x0000000000000001 r23: 0x00000000057ce800
r24: 0x0000000000000000 r25: 0x00000000a07c9d70 r26: 0x0000000000000008 r27: 0x00000000057cf0f0
r28: 0x00000000f059a250 r29: 0x0000000000000000 r30: 0x00000000057cd2a0 r31: 0x000000009082ef40
PB 15" 1.67 Mac OS X (10.4.7)

FCP quits when DV deck turned on

Similar Messages

Maybe you are looking for