1 27 28 29 30 31 32 Previous Next 478 Replies Latest reply: Apr 28, 2014 12:24 PM by Yarramalong Go to original post Branched to a new discussion.
  • 420. Re: The Final Cut Pro X CRASH Thread
    MrTT Level 1 Level 1 (0 points)

    No mr Rupeman, FCPX is till eating memory, and are unstable...

    I have tried what reto photography said, now it does not crash so often anymore..

  • 421. Re: The Final Cut Pro X CRASH Thread
    BROOKLYNTREEZ Level 1 Level 1 (120 points)

    Can u try moving the project and media to a local drive?

  • 422. Re: The Final Cut Pro X CRASH Thread
    Fergus Meiklejohn1 Level 1 Level 1 (65 points)

    I've had terrible trouble with FCPX and have just managed to get it to work using the following strategies:

     

    Firstly I'm careful not to have too many other apps open using RAM or the CPU.  Memoryfreer and Activity Monitor help to monitor and solve.

     

    Secondly I'm careful not to overtask FCPX, like not viewing audio waveforms all the time for example or rendering in the background when it is unnecessary.

     

    Thirdly I'm not putting the media on my internal drive, I'm placing it on an external FW800 drive.

     

    Fourthly and MOST IMPORTANTLY I've degragmented my drives (my internal 500GB drive was such a mess i took 20 hours to defrag..!).  I used iDefrag to do this and it is a cracking little app.  Since I did that FCPX runs much much much better :-)

     

    In general my impression of FCPX is that it is trying to do a lot of things that FCP7 would not do, or even attempt to do, and that uses huge system resources.  I'm using a 2010 MBP i7 with 8GB or RAM and external FW800 drives and FCPX only just works normally.  I suspect that FCPX is really designed for use on quadcore machines with 16GB of RAM and thunderbolt drives, that is actually the base level of performance required for normal operation.

     

    I hope this helps everyone..  iDefrag :-)  What a difference it has made to the performance of my MBP!

  • 423. Re: The Final Cut Pro X CRASH Thread
    coocooforcocoapuffs Level 3 Level 3 (845 points)

    I hope this helps everyone..  iDefrag :-)  What a difference it has made to the performance of my MBP!

     

    It might help me. I've done all of the above except the iDefrag. I have it, have tried before, but don't really understand the interface and what it's telling me. Which option do you use to defrag: quick or optimize or other? It seems to me the most fragged items on my disk are 1)logs, 2)sleepimage, 3)various dbs and the rest is slight fragmentation of all the apps and support files installed (mostly Adobe CS and related plugs) as well as plugins related to FCPX. So I am wondering, would flushing all the flushables above (#1 and #2) help? Cheers!

     

    Ps. here are the stats, which I can't tell look good or bad:

    Screen Shot 2012-03-30 at 2.06.12 PM.png

  • 424. Re: The Final Cut Pro X CRASH Thread
    Fergus Meiklejohn1 Level 1 Level 1 (65 points)

    It's difficult to say, I can only talk from my experience.  My drives, especially my internal drive, were completely fragmented, a total disaster, so iDefrag has made a real and immediate difference to my FCPX performance.  I did a full defrag, compacted and rebuilt the b-tree files.

    Your stats look alright to me, so maybe you have another issue.  In general FCPX needs massive system resources to work properly.  My big problem was my drives, I fixed them and now it works much much better for me (I also never put media on the internal drive anymore).  An example: I had media files on my internal drive and copies on a fast FW800 drive.  I reconnected the media to the external drive but FCPX secretly ignored this command and actually kept using the files on the internal drive.  Strangely that meant typing text was one.. letter.. at.. a.. time..  Incredibly slow!  Today I deleted the files on the internal drive, forced FCPX to reconnect to the same files on my defragmented FW800 drive and now everything is faster and smoother and text types on normally.  Why should this make a difference to text>>?  I have no idea.  It's crazy but it has totally changed the app's behavior.  I suspect FCPX has been designed to do all kinds of things in the background in order to give the user a totally real time experience but the irony is that on anything but a carefully managed and superfast machine this leads to meltdown and a circa 1980 user experience.  So maybe iDefrag won't work as well for you but I do suspect that there is a bottleneck somewhere in your system which you need to find, and which when you remove it will mean the app behaves much better.

  • 425. Re: The Final Cut Pro X CRASH Thread
    coocooforcocoapuffs Level 3 Level 3 (845 points)

    thx for that. my only visable problem with FCPX now is jerky playback in the viewer, and in FCP 7 I get dropped frames on playback. but i've upgraded to an unmentionable version of the cat so maybe things will smooth out later...

  • 426. Re: The Final Cut Pro X CRASH Thread
    MBD-Inc Level 1 Level 1 (0 points)

    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!!

  • 427. Re: The Final Cut Pro X CRASH Thread
    Collin_T Level 1 Level 1 (0 points)

    I had a projects corrupted, as soon as I was triying to modify my porjects, fcpx crashed.

    So I identifyed which project was the problem then:

     

    - Export my project as XML

    - Then reimport it in another empty project

     

    worked as magical

     

    you have to be shure it's the project and not the media that is corrupted

     

    cheers!

     

    Collin

  • 428. Re: The Final Cut Pro X CRASH Thread
    evilapa Level 1 Level 1 (0 points)

    I also had problems with FCPX crashing when I used the Inspector on a title. Seems some of you are having the same issue with using it on effects. I think I have solved it, at least for now. Have a look in this thread, https://discussions.apple.com/message/18447598#18447598

  • 429. Re: The Final Cut Pro X CRASH Thread
    Marc Sterling Level 1 Level 1 (5 points)

    FFThumbnailRequestManager seems to be the culprit... it's asking for a thumbnail, can't find it and crashes -WHAT SICK FUN... (forget the frickin thumbnail - I can live without it!!!)

     

    I opened my crash logs: They are in applications/utility , open the console,

    look for diagnostic reports listed under files;  ~ library/logs, there should be a list of crash reports for FCP X.

     

    look for crashed thread

    Crashed Thread:  50  BGTask: FFThumbnailRequestManager  Dispatch queue: com.apple.root.default-priority

     

    I searched "FFThumbnailRequestManager" and it shows up in every one's crash reports.

     

    That piece of code is not catching the error and crashing FCP X, looks like -- This is ****!

     

    I turned off thumbnails in the timeline yesterday - not sure if that avoids the problem..

  • 430. Re: The Final Cut Pro X CRASH Thread
    jerikofox Level 1 Level 1 (0 points)

    I share my sad little story with FCPX...  While I was doing HD-projects everything was a fairytale.  Problems started to appear when I was working with material imported from Samsung MiniDV-camera.  (I don't know if this makes any difference.)

     

    First it was this Title inspector related crashing (that everyone here seems to be a little bit too familiar with...).  Touching a certain title with inspector on caused the infinite beachball and I had to force close because FCPX was not responding.  For some reason I could edit most titles with no problems (and titles in HD-projects never caused this).  Okay, I was reading all the discussions here, there and everywhere and found out that I could avoid crashing by keeping the inspector closed.

     

    Now I was able to work again and even with inspector on every now and then.  At least changing font sizes and colours, but not the text itself (in inspector).  Until...I was doing a sideways scrolling text (ticker?) and writing some text using inspector and FCPX crashed - no beachball, just crash.  I tried to restart it, but now it crashes on start up.  Every time.

     

    Once again I did my own research on internet and found lots of useful advice I did not understand.  Until I found this site:

    http://www.lafcpug.org/Tutorials/basic_fcpx_troubleshooting.html

    (Very useful 101 tutorial for troubleshooting for us who are not pros and not native in English.)

     

    I jumped almost all the hoops it told me to:

    Updated (nothing newer was available)

    Trashed the preferences (and got Preference Manager)

    Disabled first all Events and then all Events and all Projects with Event Manager X

    Performed a Safe Boot

    Did that Disk Utility Repair stuff (nothing to repair)

    Tried use FCPX as other user

     

    After every step FCPX kept on crashing on start up until I logged in as other user.  For me it seems to like there is something wrong with my user account/folder, but I don't know what that is or what I should do.  I haven't yet read every page of this discussion, but I will.  I was wondering if I should reinstall FCPX.  If I do that what happens to my Events and Projects?  Will they stay untouched?  Should I first copy those folders to somewhere safe?

     

    I appreciate any help and wish that this story might help someone.

     

    Working with iMac with Mac OS X Lion 10.7.4, 2.8 GHz Intel Core i5, 12 GB 1333 MHz DDR3, 1T SATA hard drive and FCPX 10.0.4 + Compressor 4.0.3.

  • 431. Re: The Final Cut Pro X CRASH Thread
    go2rba Level 1 Level 1 (10 points)

    Final Cut X is stranger than you'd imagine. Tonight, for me, Final Cut X became crash on boot unusable due to a denial of service divide by zero error sent to my machine by Apple.

     

    I had this problem due to the fact when I first bought Final Cut X (at initial release) it would not work at all on my machine, and I got my money back. Months later, I bought a newer version which worked great. I began sending feedback on improving the program. A lot of feedback. Eventually someone at Apple mistakenly thought I did not own the software, because, although I had bought it twice, the first time I got my money back. Bingo, denial of service was issued. It is how Apple controls things in the App Store. Suddenly, my legit copy of Final Cut X would never work again. I complained, and it escalated up the chain, until eventually, I was told it was the App Store AND Final Cut causing the issue.

     

    My workaround was to create a new person, with a new name, and new Apple I.D. and Apple Account (my alter ego) on my machine, which brought Final Cut back to working status. I have been editing like mad since, until tonight. I have been sending in that feedback, and once again, having not fixed the App Store nor Final Cut, I am in denial of service.

     

    I think I can fix it by unplugging the network, or turning off the Internet, but, as a VOIP user, there goes my phone.  Might hafta suffer. There's a tweak edit of a two hour plus show coming in at 10 a.m.

     

    I only post here in the hope that someone of substance gets this issue resolved.

     

    Richard Brown

  • 432. Re: The Final Cut Pro X CRASH Thread
    Yarramalong Level 1 Level 1 (125 points)

    Richard,

     

    That´s not Apple or App Store. This can happen to you with a fully legal purchased copy of Windows 7. Than your entire business is down because no application will run. I had it twice with a WIN 7 copy installed on a virtual machine run under Parallels. After a crash of Mac OS X caused by Cooliris on Firefox, Windows started telling me that my copy was not legally purchased. Since it was not legally purchased, I was denied any help from Microsoft. (By the way, IBM is even smarter and would not deny service, but just ask you to enter a correct product ID before getting any other response than this request. An this for a legally purchased software.) After about two months of struggeling with the software and a variety of user forums, I decided to contact Microsoft directly. A very friendly guy went through all steps of installing the stuff with me. After about an hour, the culprit was found. Somewhere unknown to any WIN 7 user, the crash of Firefox on MACOS X had selected an option telling the Microsoft people that my copy was illegal.

     

    By the way, Cooliris has caused at least three chrashes of the OS X, not just of Firefox, with one of them crippling my computer for many days. It is a very fine and amazing piece of software - but with fatal consequences.

  • 433. Re: The Final Cut Pro X CRASH Thread
    go2rba Level 1 Level 1 (10 points)

    The apparent fix to my issue was Little Snitch. I bought it again after many years, and it keeps Final Cut X from phoning home on boot to allow the App Store to issue the divide by zero denial of service.

     

    In support of my earlier statement, I was in major communication at a very high level with Apple, and they confirmed the denial of service methodology regarding the App Store. You only need to be tainted with a refund to have a program stop working after repurchase. A glitch in the system which is being fixed.

     

    I do have Windows 7 (unbelievably awful) just to do 3D Blu Rays using Vegas (an abomination of idiotic 1957 primitivism programming.) Your comments on that are interesting, but not the issue here. I only wish Apple would buy up the 3D Blu Ray Alliance and put 3D Authoring as part of their post suite. The whole thing is not worth much compared to Apple's cash richness.

     

    Another thing about Windows, I hope everyone know that by default, many of the features of the Internet are turned off in Explorer because many features of the Internet make great roadways to corrupt that unfinished, unprotected, swiss cheese of an OS.

     

    Oh, I should mention the original fix with creating another user also involved buying Final Cut X as the new user with a new App Store account. It was my mistake to have entered the tainted email address a few times in my many feedback commentaries.

  • 434. Re: The Final Cut Pro X CRASH Thread
    MgFrobozz Level 1 Level 1 (0 points)

    Crash when loading clip into the timeline:

    https://discussions.apple.com/thread/4133473