You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: MonyMony
MonyMony Author
User level: Level 1
8 points

FCP Crashing...How to Read a Crash Report?

Hello!


I'm a bit of an amateur when it comes to Macs, so I'm wondering if someone can help.


I recently had a fellow install more memory in my tower, along with a new internal hard drive. After he did this, FCP began crashing every time it tried to play through unrendered material. It also crashes when I attempt to send footage to Compressor to create a DVD. What might be causing this?


Crash Report while running Compressor:


Process: Final Cut Pro [3268]Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut ProIdentifier: com.apple.FinalCutProVersion: 7.0 (7.0)Build Info: FCPApp-906181654~22Code Type: X86 (Native)Parent Process: launchd [127]Date/Time: 2011-06-17 13:04:23.138 -0400OS Version: Mac OS X 10.6.7 (10J869)Report Version: 6Interval Since Last Report: 100466 secCrashes Since Last Report: 12Per-App Interval Since Last Report: 159035 secPer-App Crashes Since Last Report: 8Anonymous UUID: E780A1E6-1CCD-45AC-9599-08B3B24A077DException Type: EXC_BAD_ACCESS (SIGBUS)Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000Crashed Thread: 0 Dispatch queue: com.apple.main-threadThread 0 Crashed: Dispatch queue: com.apple.main-thread0 libGLImage.dylib 0x949984cf void glgConvertTo_32<GLGConverter_ARGB8_RGBA8, (GLGMemory)2>(GLGOperation const*, GLDPixelMode const*) + 2541 libGLImage.dylib 0x94978342 glgProcessPixelsWithProcessor + 2436


Crash Report while trying to play through unrendered footage:


Process: Final Cut Pro [2580]Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut ProIdentifier: com.apple.FinalCutProVersion: 7.0 (7.0)Build Info: FCPApp-906181654~22Code Type: X86 (Native)Parent Process: launchd [127]Date/Time: 2011-06-16 23:08:50.410 -0400OS Version: Mac OS X 10.6.7 (10J869)Report Version: 6Interval Since Last Report: 50336 secCrashes Since Last Report: 9Per-App Interval Since Last Report: 108996 secPer-App Crashes Since Last Report: 6Anonymous UUID: E780A1E6-1CCD-45AC-9599-08B3B24A077DException Type: EXC_BAD_ACCESS (SIGBUS)Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000Crashed Thread: 0 Dispatch queue: com.apple.main-threadThread 0 Crashed: Dispatch queue: com.apple.main-thread0 libGLImage.dylib 0x949984cf void glgConvertTo_32<GLGConverter_ARGB8_RGBA8, (GLGMemory)2>(GLGOperation const*, GLDPixelMode const*) + 2541 libGLImage.dylib 0x94978342 glgProcessPixelsWithProcessor + 2436


Also, I'm running:


Model Name: Mac Pro

Model Identifier: MacPro5,1

Processor Name: 6-Core Intel Xeon

Processor Speed: 3.33 GHz

Number Of Processors: 1

Total Number Of Cores: 6

L2 Cache (per core): 256 KB

L3 Cache: 12 MB

Memory: 16 GB

Processor Interconnect Speed: 6.4 GT/s

Boot ROM Version: MP51.007F.B01

SMC Version (system): 1.39f11

SMC Version (processor tray): 1.39f11

Posted on Jun 17, 2011 10:24 AM

Reply
Question marked as Top-ranking reply
User profile for user: Shane Ross
Shane Ross
User level: Level 8
43,110 points

Posted on Jun 17, 2011 10:28 AM

You use the CRASH ANALYZER from the Maintenance Pack, found at digitalrebellion.com. Best software pack for users of FCP.


Your issue is...


Graphics Card

This crash appears to have been caused by an issue with your graphics card or graphics drivers.

Common causes:

  • Embedding complex Motion projects in your Final Cut Pro timeline.
  • Using a large number of layered tracks.
  • Putting lots of filters on a single clip, especially if that clip is a long-GOP format such as XDCAM or H.264.
  • Running Final Cut Studio on an underpowered graphics card.
  • Running out of graphics memory.
  • Using images in Motion that are larger than your graphics card's maximum texture size.

Suggested Actions

  • Switch off RT Extreme in Final Cut Pro.
  • Export any embedded Motion or LiveType projects on your timeline as QuickTime movies and then reimport them.
  • In Motion, switch the Fixed Resolution option on for vector and PDF images.
  • Resize any large images in your project to keep them below 4000 x 4000 pixels.
  • In Final Cut Pro, try switching off sequence thumbnails to improve stability. You can do this by going to Final Cut Pro > User Settings > Timeline Options.
  • Update your operating system, as Apple includes new graphics drivers with each OS X point update.
  • Consider purchasing a more powerful graphics card.
  • Since this crash is often caused by overworking the computer, consider the following to minimize the strain on your system:
    • Don't edit MPEG-2, H.264, XDCAM or HDV in the timeline - set your sequence codec to ProRes or else convert it to the ProRes codec.
    • Convert Motion projects to QuickTime movies. If you must have embedded Motion projects in your timeline, make sure they are not too complex.
    • Don't use your system drive as a scratch disk.
    • Make sure your scratch disk has enough throughput to playback the video format you are using plus 20% for overhead. Also make sure it has at least 20% free disk space on it.
    • If you are using multiclips, remember that each camera angle plays back simultaneously, so you need fast enough disks to play back all of your multiclip angles at once.
    • If you are using any third-party filters in your sequence, make sure they are compatible with your version of Final Cut Pro. It's worth checking with the manufacturer for an update.

More Information

This crash is related to OpenGL. Consider updating your operating system or upgrading to a card that supports a later version of OpenGL.

Relevant Line

0 libGLImage.dylib 0x949984cf void glgConvertTo_32(GLGOperation const*, GLDPixelMode const*) + 254



Report generated by Crash Analyzer in FCS Maintenance Pack

View in context
2 replies
Question marked as Top-ranking reply
User profile for user: Shane Ross
Shane Ross
User level: Level 8
43,110 points

Jun 17, 2011 10:28 AM in response to MonyMony

You use the CRASH ANALYZER from the Maintenance Pack, found at digitalrebellion.com. Best software pack for users of FCP.


Your issue is...


Graphics Card

This crash appears to have been caused by an issue with your graphics card or graphics drivers.

Common causes:

  • Embedding complex Motion projects in your Final Cut Pro timeline.
  • Using a large number of layered tracks.
  • Putting lots of filters on a single clip, especially if that clip is a long-GOP format such as XDCAM or H.264.
  • Running Final Cut Studio on an underpowered graphics card.
  • Running out of graphics memory.
  • Using images in Motion that are larger than your graphics card's maximum texture size.

Suggested Actions

  • Switch off RT Extreme in Final Cut Pro.
  • Export any embedded Motion or LiveType projects on your timeline as QuickTime movies and then reimport them.
  • In Motion, switch the Fixed Resolution option on for vector and PDF images.
  • Resize any large images in your project to keep them below 4000 x 4000 pixels.
  • In Final Cut Pro, try switching off sequence thumbnails to improve stability. You can do this by going to Final Cut Pro > User Settings > Timeline Options.
  • Update your operating system, as Apple includes new graphics drivers with each OS X point update.
  • Consider purchasing a more powerful graphics card.
  • Since this crash is often caused by overworking the computer, consider the following to minimize the strain on your system:
    • Don't edit MPEG-2, H.264, XDCAM or HDV in the timeline - set your sequence codec to ProRes or else convert it to the ProRes codec.
    • Convert Motion projects to QuickTime movies. If you must have embedded Motion projects in your timeline, make sure they are not too complex.
    • Don't use your system drive as a scratch disk.
    • Make sure your scratch disk has enough throughput to playback the video format you are using plus 20% for overhead. Also make sure it has at least 20% free disk space on it.
    • If you are using multiclips, remember that each camera angle plays back simultaneously, so you need fast enough disks to play back all of your multiclip angles at once.
    • If you are using any third-party filters in your sequence, make sure they are compatible with your version of Final Cut Pro. It's worth checking with the manufacturer for an update.

More Information

This crash is related to OpenGL. Consider updating your operating system or upgrading to a card that supports a later version of OpenGL.

Relevant Line

0 libGLImage.dylib 0x949984cf void glgConvertTo_32(GLGOperation const*, GLDPixelMode const*) + 254



Report generated by Crash Analyzer in FCS Maintenance Pack

Reply

FCP Crashing...How to Read a Crash Report?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.
Learn more Sign up