-
Strange FCP 7.0.3 Crash
This is running on a 200- MacBook pro with dual 2.66ghz processors and 8GB Ram. I suspect the graphics card is getting overloaded with rendering multiple plugins. If I am editing straight video it is not a problem. In fact the same project can be worked on indefinitely with out any crashes, once un-rendered clips are on the timeline though, I get repeated crashes. My solution so far has been to cancel the render every 15% and save, then start re-rendering again.
Here is an excerpt from the crash log:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000007095caaaVM Regions Near 0x7095caaa:
__LINKEDIT 000000007014e000-00000000701a4000 [ 344K] r–/rwx SM=COW /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio
–>
__TEXT 000000008effe000-000000008f7a4000 [ 7832K] r-x/rwx SM=COW /System/Library/Extensions/GeForceGLDriver.bundle/Contents/MacOS/GeForceGLDriverAny suggestions would be appreciated!
-
3 Replies
-
Is it crashing on the same clip (w/plugins effects etc) every time? It could be the plugin or effect is corrupt? Are you allocating enough RAM to FCP? Have you watched Console as you render to see if anything jumps out when it crashes?
-
It’s not the same clip, and not a specific plugin. I think it is when I work on 10 or so clips with different filters and do not render them. Now for example, the cut is complete and rendered, and there are no crashes.
Brian Lenihan
Video Editor/Sound Designer
http://www.floridapanthers.com
https://www.youtube.com/user/LennyLenihan -
It’s something else entirely, I don’t think it’s because of unrendered clips. It looks like the script is pointing at some components and extensions, so I would check those out. It could also be a system wide problem, such as the health of your RAM, RAID, harddrives, etc.
Reply to this Discussion! Login or Sign Up