Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy FCP crashes on start in Snow Leopard

  • FCP crashes on start in Snow Leopard

    Posted by Rick Hull on September 8, 2009 at 7:10 pm

    Final Cut Pro crashes on start up in Snow Leopard. (FCP Studio 7.) Is anyone else having this problem? Need a solution. Have tried trashing preference but did not fix it. All was very stable until Snow Leopard upgrade two days ago. Here is the crash report abbreviated:

    Process: Final Cut Pro 277
    Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
    Identifier: com.apple.FinalCutPro
    Version: 7.0 (7.0)
    Build Info: FCPApp-906181654~22
    Code Type: X86 (Native)
    Parent Process: launchd 117

    Date/Time: 2009-09-08 13:21:25.556 -0500
    OS Version: Mac OS X 10.6 (10A432)
    Report Version: 6

    Interval Since Last Report: 38871 sec
    Crashes Since Last Report: 9
    Per-App Interval Since Last Report: 3284 sec
    Per-App Crashes Since Last Report: 9
    Anonymous UUID: FF0CC1EE-2B5F-4E82-9AE4-BD938A5ABCFB

    Exception Type: EXC_BAD_ACCESS (SIGBUS)
    Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
    Crashed Thread: 0 Dispatch queue: com.apple.main-thread

    Thread 0 Crashed: Dispatch queue: com.apple.main-thread
    0 libSystem.B.dylib 0x90006ab0 strlen + 16
    1 …ple.CoreServices.CarbonCore 0x9470b5b8 FSMount::makepath(unsigned long, char const*, unsigned long, char*) + 140
    2 …ple.CoreServices.CarbonCore 0x9470786b FSMount::_getattrs(unsigned long, char const*, unsigned long, unsigned long, FSAttributeInfo*, unsigned long, unsigned char*) + 179
    3 …ple.CoreServices.CarbonCore 0x94707775 FSMount::getattrs(unsigned long, char const*, unsigned long, unsigned long, FSAttributeInfo*, unsigned long, unsigned char*) + 279
    4 …ple.CoreServices.CarbonCore 0x94752146 FindHFSName2Retained(void*, short*, unsigned long, unsigned long, FSAttributeInfo*, char*) + 1017
    5 …ple.CoreServices.CarbonCore 0x947acf6c _PBMakeFSSpecSync + 112
    6 …ple.CoreServices.CarbonCore 0x947a9be6 FSMakeFSSpec + 48
    7 com.apple.FinalCutPro 0x00188dac pKGFileExists(KGFileSpec*) + 244
    8 com.apple.FinalCutPro 0x001ae51c KGMenusLibAction + 2676
    9 com.apple.FinalCutPro 0x002452dc CallLibs(KGLibActionCode, unsigned char) + 202
    10 com.apple.FinalCutPro 0x00245548 KGInitLibraries + 24
    11 com.apple.FinalCutPro 0x002455e1 KGInit() + 75
    12 com.apple.FinalCutPro 0x004130d3 OpenApplication(AEDesc const*, AEDesc*, long) + 73
    13 com.apple.AE 0x98505de6 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 166
    14 com.apple.AE 0x98505ce5 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 43
    15 com.apple.AE 0x98505bf2 aeProcessAppleEvent + 197
    16 com.apple.HIToolbox 0x94d9d381 AEProcessAppleEvent + 50
    17 com.apple.HIToolbox 0x94f1deb8 AEProcessEvent + 160
    18 com.apple.HIToolbox 0x94e2f6a6 HIStdAppHandler::HandleEvent(OpaqueEventHandlerCallRef*, TCarbonEvent&) + 206
    19 com.apple.HIToolbox 0x94e30794 TEventHandler::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 64
    20 com.apple.HIToolbox 0x94d69129 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1567
    21 com.apple.HIToolbox 0x94d683f0 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 411
    22 com.apple.HIToolbox 0x94d6824f SendEventToEventTargetWithOptions + 58
    23 com.apple.HIToolbox 0x94d9cc0c ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 3006
    24 com.apple.HIToolbox 0x94d6957a DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2672
    25 com.apple.HIToolbox 0x94d683f0 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 411
    26 com.apple.HIToolbox 0x94d8aa81 SendEventToEventTarget + 52
    27 com.apple.HIToolbox 0x94f138f7 ToolboxEventDispatcher + 86
    28 com.apple.HIToolbox 0x94f13a2f RunApplicationEventLoop + 243
    29 com.apple.FinalCutPro 0x0015464f KGMainEvent(void*) + 51
    30 com.apple.FinalCutPro 0x002c1aa8 main + 54
    31 com.apple.FinalCutPro 0x00003a6b _start + 209
    32 com.apple.FinalCutPro 0x00003999 start + 41

    Mac Pro 8 core, 16GB RAM, AJA LHi, 3TB Raid, Dual monitors. Mac OS X (10.6)

    David Roth weiss replied 15 years, 5 months ago 14 Members · 21 Replies
  • 21 Replies
  • Tom Wolsky

    September 8, 2009 at 7:39 pm

    Did you do clean erase and install of the OS and then reinstall the application from the discs?

    All the best,

    Tom

    Class on Demand DVDs “Complete Training for FCP6,” “Basic Training for FCS2” and “Final Cut Express Made Easy”
    Author: “Final Cut Pro 5 Editing Essentials” and “Final Cut Express 4 Editing Workshop”

  • Rick Hull

    September 8, 2009 at 8:28 pm

    Thanks Tom,

    The recommended action was to install Snow Leopard over 10.5.8 so that’s what I did. Not really an option anyway given our operating schedule. Would prefer a debug that handled the specific crash thread to a complete re-install. Is there a simple way to revert to 10.5.8?

  • Joe Bryan

    September 8, 2009 at 9:47 pm

    One of our suites is doing the same thing. I thought it started when the new Kona drivers were installed. Did you install the latest drivers also?

  • Rick Hull

    September 8, 2009 at 10:20 pm

    I was using the older Kona drivers when it first started. Then installed 7.0.1 and it solved it for one day. Then it happened again. I traced this second crash to the permissions on my Raid drive. Apparently Snow Leopard is not happy with the existing permissions set by 10.5.8. I unmounted the raid drive, unlocked the permissions, put them back the way they were and rebooted Snow. It worked, and so far I’m still up in FCP. Let’s hope it stays that way!

    Seems like the KONA drivers and the Raid permissions were separate problems causing the same crash at start up in FCP.

  • Dave Jenkins

    September 9, 2009 at 3:34 am

    Sorry can’t help you with the crashes but I have been running Snow Leopard and FCS 3 that were clean installed and haven’t had one problem. Working with FCP, Motion, Color, Compressor and DVDSP all work fine.

    Dajen Productions, Santa Barbara, CA
    MacPro Two 2.8GHz Quad Core – AJA Kona LHe
    FCS 3 OS X 10.6 QT 10

  • Zane Barker

    September 9, 2009 at 5:12 am

    [Rick Hull] “The recommended action was to install Snow Leopard over 10.5.8”

    Recommended by who, certainly not the people on the COW.

    If you run Pro Apps it is ALWAYS recommended to do a clean install of any new OS.

    There are no “technical solutions” to your “artistic problems”.
    Don’t let technology get in the way of your creativity!

  • David Roth weiss

    September 9, 2009 at 5:18 am

    [Zane Barker] “Recommended by who, certainly not the people on the COW.”

    Zane,

    Something tells me you got that right. Perhaps Rick should search for “Snow Leopard 101: For Smart People Only” if he doubts you.

    David

    David Roth Weiss
    Director/Editor
    David Weiss Productions, Inc.
    Los Angeles

    POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

    A forum host of Creative COW’s Apple Final Cut Pro, Business & Marketing, Indie Film & Documentary, and Film History & Appreciations forums.

  • Jiri Fiala

    September 9, 2009 at 4:39 pm

    I am on clean installation of FCP7 and Snow Leopard and it’s a crash ride too. It crashes all the time. I’m seriously contemplating moving back to 10.5.8.

  • Jacques Azur

    September 10, 2009 at 7:39 pm

    You did make a sparseimage of 10.5.8 system partition before the upgrade, right?

  • Tom Fuldner

    September 14, 2009 at 1:53 am

    I’m having the same experience with FCS3 and SL. FCP7 crashes by itself; when round-tripping to Color and Soundtrack Pro.

    It’s like owning a PC two years ago and upgrading to Vista: uggh.

    The 10.6.1 update hasn’t contributed any greater degree of stability. In the mean time, I’m saving my FCP sequences much more frequently.

    Deleting preference files in Adobe Soundbooth and Office 2008 for Mac has improved their stability. Tempted to do the same with FCP, except I’m leery of making things worse while I’ve got projects due.

    Tom

    Tom F.
    Raleigh, NC

Page 1 of 3

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy