Resolved iMovie 11 Suddenly Won't Open

Discussion in 'Mac Apps and Mac App Store' started by MewingFugur, Jun 25, 2012.

  1. MewingFugur, Jun 25, 2012
    Last edited: Jun 25, 2012

    MewingFugur macrumors newbie

    Joined:
    Feb 5, 2011
    #1
    First off, I've read on several other forums and tried techniques that didn't work, but I will be glad to try them again. So, I tried to open iMovie today (I use it about once a week or so) and it will bounce a few time and come up with an error report saying "iMovie quit unexpectedly". I'm running Mac OS X 10.7.4 on my Mac Mini 2010. Any ideas? If you need more info, just tell me. Thanks.
     
  2. SandboxGeneral Moderator

    SandboxGeneral

    Staff Member

    Joined:
    Sep 8, 2010
    Location:
    Orbiting a G-type Main Sequence Star
    #2
    Look in Console and see what the error reports are showing for iMovie. There may be clues in there. You can also try deleting the app and reinstalling it.
     
  3. MewingFugur thread starter macrumors newbie

    Joined:
    Feb 5, 2011
    #3
    I have already deleted it and reinstalled it with the iLife disk. Here is the log I get, I didn't post the binaries because they are so long, but tell me if I do.
    ----------------------------------------------
    Process: iMovie [35095]
    Path: /Applications/iMovie.app/Contents/MacOS/iMovie
    Identifier: com.apple.iMovieApp
    Version: 9.0 (1073)
    Build Info: iMovieApp-10730000~16
    Code Type: X86 (Native)
    Parent Process: launchd [992]

    Date/Time: 2012-06-25 18:55:03.871 -0500
    OS Version: Mac OS X Server 10.7.4 (11E53)
    Report Version: 9

    Interval Since Last Report: 98588 sec
    Crashes Since Last Report: 36
    Per-App Crashes Since Last Report: 5
    Anonymous UUID: 2589A89A-9402-4F93-B079-339E3E107727

    Crashed Thread: 0 Dispatch queue: com.apple.main-thread

    Exception Type: EXC_BAD_ACCESS (SIGBUS)
    Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000034

    VM Regions Near 0x34:
    --> __PAGEZERO 0000000000000000-0000000000001000 [ 4K] ---/--- SM=NUL /Applications/iMovie.app/Contents/MacOS/iMovie
    __TEXT 0000000000001000-0000000000412000 [ 4164K] r-x/rwx SM=COW /Applications/iMovie.app/Contents/MacOS/iMovie

    Application Specific Information:
    objc[35095]: garbage collection is OFF

    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0 dyld 0x8fe83063 dyld::registerAddCallback(void (*)(mach_header const*, long)) + 61
    1 libdyld.dylib 0x03726078 _dyld_register_func_for_add_image + 74
    2 libignitor.dylib 0x004c8e76 initializer + 27
    3 dyld 0x8fe91203 ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 251
    4 dyld 0x8fe90d68 ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 64
    5 dyld 0x8fe8e2c8 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 256
    6 dyld 0x8fe8f268 ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 62
    7 dyld 0x8fe83664 dyld::initializeMainExecutable() + 166
    8 dyld 0x8fe87f99 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**) + 2238
    9 dyld 0x8fe812ef dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*) + 637
    10 dyld 0x8fe81063 _dyld_start + 51

    Thread 0 crashed with X86 Thread State (32-bit):
    eax: 0x8fe83034 ebx: 0x0c46e000 ecx: 0x004c8e7c edx: 0x00000000
    edi: 0x8feb6dac esi: 0x00000000 ebp: 0xbfffe9a8 esp: 0xbfffe980
    ss: 0x00000023 efl: 0x00010286 eip: 0x8fe83063 cs: 0x0000001b
    ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
    cr2: 0x00000034
    Logical CPU: 1
     
  4. SandboxGeneral Moderator

    SandboxGeneral

    Staff Member

    Joined:
    Sep 8, 2010
    Location:
    Orbiting a G-type Main Sequence Star
    #4
    I didn't see anything that would be useful. I did however once have a similar problem with iMovie that I couldn't figure out. What ended up solving it was the removal of Adobe Flash and then reinstalling it.

    There was no rhyme or reason for it, but it did work for me.
     
  5. MewingFugur thread starter macrumors newbie

    Joined:
    Feb 5, 2011
    #5
    Thanks for the input but it didn't work. :(
     
  6. SandboxGeneral Moderator

    SandboxGeneral

    Staff Member

    Joined:
    Sep 8, 2010
    Location:
    Orbiting a G-type Main Sequence Star
    #6
    Have you since restarted the computer after the iMovie problems?

    I'm all out of ideas on this one, perhaps someone else can chime in and recommend something.

    I hate to say it, but if all else fails, reinstall OS X. But that's a long shot and not really what we want to do just for one faulty application.
     
  7. MewingFugur thread starter macrumors newbie

    Joined:
    Feb 5, 2011
    #7
    Yep, I've even booted into safe mode and tried opening it there but it came up with "iMovie requires a graphics card that is compatible with Quartz Extreme. One or more of your graphics cards does not support Quartz Extreme." but I suspect that has something to do with safe mode.

    Thanks
     
  8. AdeFowler macrumors 68020

    AdeFowler

    Joined:
    Aug 27, 2004
    Location:
    England
    #8
    Are you using a font manager? I use FontExplorer and had turned off some of the less than useful fonts that get installed by iLife. iMovie refused to launch unless I reenabled the required fonts.
     
  9. MewingFugur thread starter macrumors newbie

    Joined:
    Feb 5, 2011
    #9
    Once again...nope....thanks though.
     
  10. MewingFugur thread starter macrumors newbie

    Joined:
    Feb 5, 2011
    #10
    Fixed

    So...please don't consider me a total idiot, but it just so happened that I didn't think of checking for software updates, which solved the problem. For those of you who stumble upon this thread in the future, a solution ( that I used when this happened about a month ago but was easily fixed) is to go to your disk utilities app. Once there, click on Macintosh HD, and click repair permissions. Hopefully that helps! Thanks to everyone who tried to help.
     

Share This Page