-
FCP crashing after multiple captures…
I’ve been getting strange hangs and crashes today after multiple captures in FCP. I work for a Windows based gaming company, so our I.T. department has a hard time figuring out problems with my Mac Pro, forcing me to try and figure it out for myself. Here’s my work flow:
From an Xbox 360 set to output 720p video and stereo audio via HDMI to a Blackmagic Multibridge Pro connected to my Mac Pro running OS X 10.6.1 (Snow Leopard). Capturing live via FCP using the Blackmagic 720p 59.94 ProRes (HQ) codec to a RAID array. Using Blackmagic’s disk speed utility, I should be able to capture 720p to that drive without a problem, and I HAVE been for the last three to four months (since I switched to a Mac based capture solution). Now I can capture one clip and sometimes a second clip, but usually by the third clip either the capture will fail to start or fail to stop. I just get the pinwheel of death until either FCP crashes or I have to force quit it.
I downloaded Digital Rebellion’s FCS Maintenance Pack and it’s Crash Analyzer utility can’t determine what the problem is either. I’ve trashed preferences and render files. I’ve even gone as far as using FCS to uninstall FCP and then restarting my system and reinstalling. No luck…
I now turn to you dear COWs in hopes that you can help me out of my quandary. Here is the crashed thread log according to the FCS crash utility. Hope it helps:
0 com.apple.DesktopServices 0x961d69e0 TNode::RemovePtrReference() + 10
1 com.apple.DesktopServices 0x961d699a TNodePtr::operator=(TNodePtr const&) + 36
2 com.apple.DesktopServices 0x961ddebd TNotifier::TNotifier(TCountedPtrconst&, TNodePtr const&, TNodePtr const&) + 101
3 com.apple.DesktopServices 0x961e358e TNodeRequest::TNodeRequest(TClientChangeNotifier const*) + 150
4 com.apple.DesktopServices 0x961e18f4 TNode::HandleRecursiveListeners() + 322
5 com.apple.DesktopServices 0x9622eaf0 TNode::HandleChange(char*, unsigned long, TCountedPtrconst&) + 1658
6 com.apple.DesktopServices 0x961ec9a8 TSystemNotificationTask::HandleFileChanged(__FSEventStream const*, void*, unsigned long, void*, unsigned long const*, unsigned long long const*) + 124
7 …ple.CoreServices.CarbonCore 0x91424b58 implementation_callback_rpc + 1685
8 …ple.CoreServices.CarbonCore 0x9142442c _Xcallback_rpc + 360
9 …ple.CoreServices.CarbonCore 0x9142429d FSEventsD2F_server + 74
10 …ple.CoreServices.CarbonCore 0x9142424c dispatch_rcv_msg + 24
11 libSystem.B.dylib 0x9902a357 dispatch_mig_server + 232
12 libSystem.B.dylib 0x9902a262 __dispatch_source_mig_create_block_invoke_1 + 173
13 libSystem.B.dylib 0x9900422c _dispatch_source_latch_and_call + 62
14 libSystem.B.dylib 0x98ff70a2 _dispatch_source_invoke + 210
15 libSystem.B.dylib 0x98ff5bf9 _dispatch_queue_invoke + 183
16 libSystem.B.dylib 0x98ff614d _dispatch_queue_drain + 258
17 libSystem.B.dylib 0x98ff5b77 _dispatch_queue_invoke + 53
18 libSystem.B.dylib 0x98ff598a _dispatch_worker_thread2 + 234
19 libSystem.B.dylib 0x98ff5401 _pthread_wqthread + 390
20 libSystem.B.dylib 0x98ff5246 start_wqthread + 30 -
1 Reply
-
Snow Leopard has some serious underlying file system problems. It is not ready for primetime at all. I’ve received a lot of crash logs from open / save dialogs in 10.6.1, but interestingly not 10.6.0. So on that anecdotal evidence, it might be worth downgrading to 10.6.0 to see if the problem goes away and if not, hope that 10.6.2 fixes it.
Reply to this Discussion! Login or Sign Up