nfoo

Q: The Final Cut Pro X CRASH Thread

Hi, I'd like to start a thread for people that experience crashed in Final Cut Pro X.

No other Applications crashes on my Mac Pro. I have never experienced crashes like

I do now with Final Cut Pro X.

 

During my three hours spend with FCPX it crashed about 8 - 9 times.

The Crash reporter seems to indicate that is related to the functions that use the Video Card acceleration.

It's always OpenCL / OpenGL ...

 

Please Post if your's crashes, too.

Mac Pro, Mac OS X (10.6.7), 6 Core, 8 GB RAM, Ati 5870

Posted on Jun 21, 2011 11:08 AM

Close

Q: The Final Cut Pro X CRASH Thread

  • All replies
  • Helpful answers

first Previous Page 16 of 32 last Next
  • by gypsie2012,

    gypsie2012 gypsie2012 Sep 7, 2011 8:02 PM in response to RogerOut
    Level 1 (0 points)
    Sep 7, 2011 8:02 PM in response to RogerOut

    Dear man, I am ALL grown up (but stil I am willing to learn this every day). Yet, your comment comes across as someone MORE frustrated than I am with trying to make something work.  Don't you want things to work instead of trashing someone's post?

    Just saying.

    P.S.: Too bad you had NOTHING to contribute to my willingness to use FCP X - unlike the shower of editors out there who felt betrayed by Apple in June.

     

    Then again, you may have NOTHING else to contribute than venom.  Maybe my posting a crash report offends you.  Meanwhile, I am offended by Apple selling something that does NOT work.

  • by stuntbrian,

    stuntbrian stuntbrian Sep 7, 2011 8:07 PM in response to RogerOut
    Level 1 (0 points)
    Sep 7, 2011 8:07 PM in response to RogerOut

    *******, that's funny.  I've been sitting here working on a project in FCPX that I jumped into right away.  I've been ******* and moaning about all the crashes, the slowness, and writing nasty comments in the crash logs.  But I have to laugh RogerOut, because you're right.  Should have waited.  Nuts.  I'm just finishing this thing up and if it weren't for the subtitling I'm doing, I would have exported it back to FCP7 as a QT file long ago.  But I kept being an idiot.  I will say though, that I did it.  For better or for worse.  It put more hair on my chest.  And I'm 50.  Wish they wouldn't have released it so soon though. It's really half-baked.  Reminds me of the first release of ClarisWorks back in the day.  Actually, that was pretty solid.  But I digress.

  • by Andy Neil,

    Andy Neil Andy Neil Sep 7, 2011 8:14 PM in response to gypsie2012
    Level 4 (3,795 points)
    Sep 7, 2011 8:14 PM in response to gypsie2012

    Not defending or attacking anyone...

     

    Posting the entire crash report isn't usually necessary.  At the top of your crash report it tells you which thread crashed (in your case Thread 0).  I've found that posting only the top of the report, and the offending thread is the best way to go about posting a crash thread.

     

    Most people on these forums don't/can't read crash threads (including myself).  I'm pretty sure Jon can, but he's an exception.

     

    Sometimes crash reports can be helpful for those who can read/diagnose them, so don't feel like you shouldn't post one, just understand that you may get more help from the community by giving as much info as you can about the specifics of your issue (how much RAM, what other programs you're running, the exact steps that lead to the crash).

     

    Andy

  • by gypsie2012,

    gypsie2012 gypsie2012 Sep 7, 2011 8:19 PM in response to Andy Neil
    Level 1 (0 points)
    Sep 7, 2011 8:19 PM in response to Andy Neil

    Thank you Andy!

     

    Kind and helpfull answer.

     

    I do not believe I know everything I NEED to know, but certainly, (at this point anyways), I believe APPLE should be aware of the "idea" that the FCP X crashes A LOT.  Sorry to all of you out there trying to help each other with this new application.  I am only trying to make my part in holding Apple accountable to some extent.  They are NOT accountable for what I do not know but they are accountable if I pay for something that does not work.

  • by gsub,

    gsub gsub Sep 8, 2011 10:20 AM in response to gypsie2012
    Level 1 (5 points)
    Sep 8, 2011 10:20 AM in response to gypsie2012

    Bonjour everybody !

    I'm happy (as Droopy was).

    I stop using FCPX.

    Crashes: about 10 in every session.

    Changed my graphic card, deleted FCE from my HD, deleted prefs, and still a lot of crashes (titles, non-US fonts, slow working, many more things).

    I paid FCPX, I use Mac(s)/Apple since 1995, it's the first time I get such a crashingapp.

    My Mac is MacPro 8 gb, Lion, GC HD 5770, no other app is so un-usable than FCPX.

    I must add that after each crash I send bug report to Apple, but when I look my modem/"routeur" ADSL, I never see any activity telling me the bug report has been sent to Apple.

    So, I keep FCPX away for some time, wishing a new version come soon (and a new MacPro too?).

    It's like buying a brand new car and keep it in your garage(not band).

    Very sad

  • by Omnimaxuk,

    Omnimaxuk Omnimaxuk Sep 9, 2011 6:12 AM in response to gsub
    Level 1 (0 points)
    Sep 9, 2011 6:12 AM in response to gsub

    FCPX still keeps crashing my MBP 13" i7 running Lion. Even after installing the latest update in Lion. So I have installed and run MacKeeper 1.8.1 which has got rid of all spurious apps and left overs from old programmes. Though there wer'nt many. I also installed Desktop monitor so I could see what was going on when running FCPX. An interesting result has occured. Every time I run FCPX and start editing any film work (no matter what type of editing is going on) Memory Usage of Used Memory goes up rapidly. Free memory gradually runs out and as it does FCPX gets slower and slower. Eventually there is no more free RAM and the programme crashes. This is what happens every time. YOu run out of memory. I have 8GB installed and that is all used very quickly by FCPX. The only way I can get arround it is to used Memory Freer and free up memory as I see it get below 1GB. Also I notice that the CPU useage is not excessively high whilst this is goin on.

     

    I hope this helps as I am getting very frustrated about the whole issue now as all of you are and Apple seems to take the position that it is so big in the world it does not need to address our concerns and issues. Nor do they attempt to inform anyof us that they know of the issue and are working on it. Or maybe they're not. However, I wait patiently.

  • by gsub,

    gsub gsub Sep 9, 2011 9:35 AM in response to Strava
    Level 1 (5 points)
    Sep 9, 2011 9:35 AM in response to Strava

    It would be very useful to create a new thread: FCPX never crashed, so the lot of people (like me) having crashes and crashes should know the right way to heaven

    Testing all the "solutions" found here never helped me, and as I read from Strava even a clean install, memory and so on, Apple MUST QUICKLY resolve all (or 99%) the problems July, August, mid-September, nothing, nothing, nothing

  • by dan28088,

    dan28088 dan28088 Sep 9, 2011 2:19 PM in response to nfoo
    Level 1 (0 points)
    Sep 9, 2011 2:19 PM in response to nfoo

    With a Mac Pro 2x2.8 GHz having 14 GB Ram FCP-X is the only application from Mac that I have ever run which can and does regularly trash my system. 

     

    I am running iCleamMemory too - not so much because I am paranoid about memory, but it's an interesting way to watch the memory leaks in FCP-X.

     

    As for crash reports - I find they are some what varying.  It may crash when I add text, when I add a new Transition, when I try and crop a photo, when I try and rescale the time line --- perhap even when I am simiply breathing.

     

    I have found that in some cases it gets stuck on one particular photo (I am working with slide shows more than video), and if I can delete the problematic photo then I can re-add it and get beyond at least that issue. 

     

    Yesterday I had the worst of all crases yet - not sure if anyone else has seen this, but have not found a posting about it.

     

    I didn't get a crash report, or any other notification - my screen simply went blank.   The computer was entirely non-responsive.   Only option was to hold the main power button down.   Back with some other applications I did once or twice get that grey screen that basically bespeaks a kernal pannic and tells you that there is no option but to power down - but this total loss of the screen and control - wow, that was new.

     

    Upon rebooting to my horror I found that the project I had been working on for the past 4 weeks was GONE.  Attempting to select it from the Finder got me the terrifying message that it was corrupt.  

     

    Time Machine had captured it earlier in the day, but the initial attempts to revive that wasted an hour for each recovery and had isseus where the recovery failed as well... no idea why.  Disk Utility reports that the Time Machine volume is fine - my best guess is that with the regular and un-predictable crashing of FCP-X it dumped during a backup and that created something wrong in the record.

     

    Restoring from a few days ago finally worked - but also lost a lot of work product.

     

    So - it seems a good idea to insure that now and again I have actually shut down FCP-X and then forced a Time Machine Backup that I know to be healthy.   

     

    The other thing I have opted to do is to start creating copies of my project - not to work with them, but to have them as safeguards against the fear of loosing something that I have spent weeks developing.   Sure, it eats up disc space - but had I been doing this earlier, I would not have been in nearly a state of panic as I was yesterday.

     

    Really surprized at how long it is taking Apple to get even one patch file out for this.   If it was something inate to my system and configuration that would be one thing, but there seem enough others experiencing the same thing that I don't believe it's just my luck with my system.

     

    Truly hoping not to see the smoking hole crash again - and hoping to see something from Apple or another creative sole sheading some light on how to fix some of the issues here.

     

    Cheers -

  • by stuckfootage,

    stuckfootage stuckfootage Sep 9, 2011 2:31 PM in response to dan28088
    Level 4 (3,040 points)
    Sep 9, 2011 2:31 PM in response to dan28088

    dan28088 wrote:

    The other thing I have opted to do is to start creating copies of my project - not to work with them, but to have them as safeguards against the fear of loosing something that I have spent weeks developing.

    Good idea! It is possible to do professional work using beta software, but you do have to be meticulous about maintaining multiple copies of everything.

  • by RogerOut,

    RogerOut RogerOut Sep 12, 2011 5:27 PM in response to gypsie2012
    Level 1 (89 points)
    Sep 12, 2011 5:27 PM in response to gypsie2012

    gypsie2012 wrote:

     

    Dear man, I am ALL grown up (but stil I am willing to learn this every day). Yet, your comment comes across as someone MORE frustrated than I am with trying to make something work.  Don't you want things to work instead of trashing someone's post?

    Just saying.

    P.S.: Too bad you had NOTHING to contribute to my willingness to use FCP X - unlike the shower of editors out there who felt betrayed by Apple in June.

     

    Then again, you may have NOTHING else to contribute than venom.  Maybe my posting a crash report offends you.  Meanwhile, I am offended by Apple selling something that does NOT work.

     

    Well guys and gals, I apologize for my little outburst.  It was uncalled for.

     

    When I have a stable workstation, I don't install any updates of any kind, and if I need to, like a ProApps update, I do it on a test machine first.  We depend on these workstations, so we protect them like crazy.  Fresh OS install, FCP Studio, required updates, and that's all that I put on them. 

     

    Believe me, I was tempted to buy X but as I kept looking at it, it clearly wasn't ready.  And even if I had bought it, it would be installed on a test machine only.

     

    I'm about to build another workstation and it will not even get Lion.  It will be Snow Leopard and FCP Studio.  We'll wait another year or so before using X.  Why?  Because Studio works and there's nothing in X that we need.  Certainly not the current headaches.

     

    So, I repeat my advice.  If you're determined to work with X, do it, you know what to expect: Unstable and lots of crashes.   If your workstation is your livelihood, use something that works day in and day out, don't mess with it and you'll sleep better at night. 

  • by RogerOut,

    RogerOut RogerOut Sep 12, 2011 5:30 PM in response to stuntbrian
    Level 1 (89 points)
    Sep 12, 2011 5:30 PM in response to stuntbrian

    Stunt, I'm 56 (and computing since 1980), so we're even. 

     

    Believe me, I had to learn the hard way myself.

  • by cris blaze,

    cris blaze cris blaze Sep 24, 2011 12:33 PM in response to Mr. Projects
    Level 1 (0 points)
    Sep 24, 2011 12:33 PM in response to Mr. Projects

    same for me....after the update does not open at all anymore....THERE IS NO WORD TO EXPLAIN MY FRUSTRATION

  • by cris blaze,

    cris blaze cris blaze Sep 24, 2011 12:37 PM in response to gsub
    Level 1 (0 points)
    Sep 24, 2011 12:37 PM in response to gsub

    THERE IS NO WORD TO EXPLAIN MY FRUSTRATION

  • by cris blaze,

    cris blaze cris blaze Sep 24, 2011 12:38 PM in response to cris blaze
    Level 1 (0 points)
    Sep 24, 2011 12:38 PM in response to cris blaze

    THERE IS NO WORD TO EXPLAIN MY FRUSTRATION

  • by MacvideoHD,

    MacvideoHD MacvideoHD Sep 25, 2011 6:25 PM in response to thierryfromanglet
    Level 1 (0 points)
    Sep 25, 2011 6:25 PM in response to thierryfromanglet

    I won't say this is the fix all, but do you ever fix your disk permissions? If not, you should.

first Previous Page 16 of 32 last Next