Skip navigation

FCPX crashes constantly

1273 Views 12 Replies Latest reply: Jun 28, 2012 12:28 AM by darfrazier10 RSS
Micha Goldfine Calculating status...
Currently Being Moderated
Feb 5, 2012 2:38 AM

I am a Premiere Pro users and tried FCPX for a few hours. I am running it on a 2008 MBP with plenty of RAM. It crashes without warning. never had an Apple software crash on me except in the 90th using the old Apple OS.

 

Just another thread to let Apple know that even if they give this for free I won't bother using it. better to use the stable iMovie or Premiere.

 

Thanks

 

Mic

  • Ian R. Brown Level 6 Level 6 (17,495 points)
    Currently Being Moderated
    Feb 5, 2012 5:24 AM (in response to Micha Goldfine)

    Although some people complain of constant crashes, FCP X works perfectly fine for most.

     

    So there is probably something about your computer setup or working methods that  is causing the problem.

     

    I am not claiming that FCP X is 100% bug free   .   .   .  .  no app is, but the majority of users do not experience the severe problems we read about on these forums.

     

    Try trashing the preferences with this free app  http://www.digitalrebellion.com/prefman/  and open Disk Utility and run Repair Disk Permissions

     

    If you are not in the habit of switching off your Mac each night, try restarting it.

  • Michael Ryan. Level 4 Level 4 (1,445 points)
    Currently Being Moderated
    Feb 5, 2012 6:36 AM (in response to Ian R. Brown)

    Hello All,

     

    I've been using FCPX since it came out and haven't had any problems.  Works 100% of the time.  I know 10 other people who use FCPX and they have never had a problem either.

     

    MIke

  • seattlex Calculating status...
    Currently Being Moderated
    Mar 9, 2012 6:33 PM (in response to Micha Goldfine)

    I found FCPx crashed 6 times in the course of a few hours.

    What resliance I have to keep on trying...

     

    And trying it was....

     

    It seemed to happen whenever I would attempt to edit the text in a title.

     

    for reference:

    on a clean boot in a new user with nothing else running

    4gb mbpro 15"

     

    So very frustrating.

     

    FCP was also taking 2-3 min to load.

    I found a recommend to delete the preferences....

    I did

    it seemed to load faster this time.

     

    Who knows....

     

    Hopefully it will get better?

    michael

  • darfrazier10 Calculating status...
    Currently Being Moderated
    Mar 24, 2012 11:31 AM (in response to seattlex)

    Same here.  New MacBook Pro 9 months ago as well as FCPX.  I'm a heavy editor and it crashed like 50 times since then. I checked Disk Utility on my external Lacie HD and says that it's OK.  Disk Utility also says MacBook is fine.  I'm thinking about re-installing FCPX but I have so many plugins!  Hmm...  Thanks for your time and forthcoming advices.  - Darren (Seattle)

  • Andrew Burke Calculating status...
    Currently Being Moderated
    Mar 24, 2012 2:11 PM (in response to darfrazier10)

    Hey darfrazier,

     

    From my experience, RAM is a huge factor in FCPX. For instance, I had many crashes using 4GB, some crashes using 8GB, and hardly any crashes with 16GB.

     

    I thinks Apple's minimum requirements (4GB RAM) are very unrealistic. I'd say the minimum to stay happy and creative is 8GB, and for a pro with serious deadlines, it's 16GB.

     

    Don't think I'm a RAM snob, either :) FCP 6 works just fine with 2GB.

     

    -Andrew

  • darfrazier10 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Mar 24, 2012 3:51 PM (in response to Andrew Burke)

    Hi Andrew:

     

    Well I have 8GB 1333 mhz ddr3, 2.3Ghz, i7, version 10.7.3.  I have about 100 GB available on my macbook.  Surely, that's GOOD enough to run FCPX for a medium-content daily usage by an editor like me.

     

    I'm gonna remove and reinstall fcpx.  I removed the preferences.  We'll see if that'll do!  :-)

     

    - D

  • Russ H Level 6 Level 6 (12,945 points)
    Currently Being Moderated
    Mar 24, 2012 4:09 PM (in response to darfrazier10)

    If you haven't seen them, here are Apple's recommendations for troubleshooting performance problems.

     

    I haven't yet logged that many miles on FCX, but my experience is somewhere in the middle of those who have thrown up their hands and headed for the exits and the enthusiasts. No question about RAM however, it can sequester all I have in the course of an editing session and bring my machine to a crawl. But I'm still interested…

     

    Good luck sorting it out.

     

    Russ

  • Andrew Burke Level 1 Level 1 (15 points)
    Currently Being Moderated
    Mar 24, 2012 4:59 PM (in response to darfrazier10)

    darfrazier,

    I think you're right on about having a machine that's capable-- yours seems to be.

     

    Let's see if the reinstall cures it.

     

    Also, you can write to Apple and discuss performance issues. When you get X running again, you can select Final Cut Pro-> Provide Feedback. I did this early on.

  • darfrazier10 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Mar 26, 2012 11:51 AM (in response to Andrew Burke)

    Good news, Andrew and everyone.

     

    Don't you hate it when it's not the bigger issues but the smallest issue that solves the problem?!?!  GAWD!

     

    I tried and tested everything -- doing the theory of reduction!  Checked external Lacie HD, MacBook, RAM, FCPX Preferences, remove/reinstall FCPX, etc.  Nothing worked until I did this...

     

    I simply "DUPLICATE" the original editing track under Projects and renamed it.  I removed the original track. Rebooted.  Started editing on the "duplicated" track.  So far, so good.  No crashes.  Geez.  That's it, yes, THAT IS IT!

     

    Moving on!  Hope this little trick will helpful for others who are dealing with what I was dealth with!

     

    Thanks everyone!

  • MBD-Inc Level 1 Level 1 (0 points)
    Currently Being Moderated
    Apr 23, 2012 2:21 PM (in response to darfrazier10)

    I'm having an issue as well with FCPX crashing all of a sudden. I got to a finishing point of my video, then I started to add grx and then it suddenly quits on me. I deleted all the grx, trashed my preferences, and I'm still coming up with this crash thread:   I can't even keep my project open now without it crashing.

     

    Thread 135 Crashed:  BGTask: FFRenderStateTracker  Dispatch queue: com.apple.root.default-priority

    0   com.apple.ProAppsFxSupport              0x000000010296a6f5 HgcMotionBlur::RenderTile_AVX(HGTile*) + 1877

    1   com.apple.ProAppsFxSupport              0x0000000102969e3a HgcMotionBlur::RenderTile(HGTile*) + 10218

    2   com.apple.Helium.HeliumRender           0x0000000102cc1569 HGRenderer::RenderTile(HGExecutionUnit*, __m128*, HGRect, HGNode*, int) + 3817

    3   com.apple.Helium.HeliumRender           0x0000000102cc169e HGRenderer::RenderTile(HGExecutionUnit*, __m128*, HGRect, HGNode*, int) + 4126

    4   com.apple.Helium.HeliumRender           0x0000000102cc169e HGRenderer::RenderTile(HGExecutionUnit*, __m128*, HGRect, HGNode*, int) + 4126

    5   com.apple.Helium.HeliumRender           0x0000000102cc169e HGRenderer::RenderTile(HGExecutionUnit*, __m128*, HGRect, HGNode*, int) + 4126

    6   com.apple.Helium.HeliumRender           0x0000000102cc169e HGRenderer::RenderTile(HGExecutionUnit*, __m128*, HGRect, HGNode*, int) + 4126

    7   com.apple.Helium.HeliumRender           0x0000000102cc169e HGRenderer::RenderTile(HGExecutionUnit*, __m128*, HGRect, HGNode*, int) + 4126

    8   com.apple.Helium.HeliumRender           0x0000000102cc169e HGRenderer::RenderTile(HGExecutionUnit*, __m128*, HGRect, HGNode*, int) + 4126

    9   com.apple.Helium.HeliumRender           0x0000000102cc169e HGRenderer::RenderTile(HGExecutionUnit*, __m128*, HGRect, HGNode*, int) + 4126

    10  com.apple.Helium.HeliumRender           0x0000000102cc0995 HGRenderer::RenderTile(HGExecutionUnit*, __m128*, HGRect, HGNode*, int) + 789

    11  com.apple.Helium.HeliumRender           0x0000000102cc169e HGRenderer::RenderTile(HGExecutionUnit*, __m128*, HGRect, HGNode*, int) + 4126

    12  com.apple.Helium.HeliumRender           0x0000000102cc169e HGRenderer::RenderTile(HGExecutionUnit*, __m128*, HGRect, HGNode*, int) + 4126

    13  com.apple.Helium.HeliumRender           0x0000000102ce6c99 ExecuteUnitGCD(void*) + 1449

    14  libSystem.B.dylib                       0x00007fff8a68c2b0 _dispatch_worker_thread2 + 206

    15  libSystem.B.dylib                       0x00007fff8a68bc08 _pthread_wqthread + 353

    16  libSystem.B.dylib                       0x00007fff8a68baa5 start_wqthread + 13

     

    I'm not really sure what it means, but if anyone can direct me in the right direction I would appreciate it. I have a deadline on this project coming up fast.

     

    Thanks!!

  • inte_moto Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jun 15, 2012 7:08 AM (in response to Micha Goldfine)

    Brand new 750GB blank hard drive, 8GB 1333 MHz DDR3, 2.4 GHz Core 2 Duo, fresh install of Lion 10.7.4, installed only the Adobe CS4 suite, Motion, and FCPX.

     

    Created a new project (only project in FCP at this point) - FCPX crashes constantly just previewing media in the event library.

  • darfrazier10 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jun 28, 2012 12:28 AM (in response to Andrew Burke)

    I removed and re-installed.  no luck.  I think its a corrupted editing track from duplicates.  Hmm... Will reply to Apple via Feedback.  Thanks!

Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.