# Bug Tracker

This page is dedicated to keeping track of the latest Final Cut Pro bugs and issues.

You can read on recommendations on if you should update Final Cut Pro here.

We keep track of these bugs via our GitHub issues site.

GitHub is a safe and secure developers platform used by over 73 million users worldwide.

To submit a new bug report, simply sign up for a free GitHub account and post an issue here.

If you'd prefer not to use GitHub, then you can always email us your bug report: [email protected]

Whenever posting a new bug/issue to GitHub, we also submit feedback directly to Apple via Feedback Assistant.

You can also send feedback directly to the Final Cut Pro team via their Feedback Form, however, unlike Feedback Assistant you can't track your request or add additional information after submitting, nor can you have a discussion with the Apple team via the comments - so we generally recommend you use Feedback Assistant as well.

# Finding Crash Logs

You can find previous crash logs in this folder:

~/Library/Logs/DiagnosticReports/

You can find your user library by holding down OPTION when you click the Go menubar item from Finder.

Because crash logs are really large, the easiest way to share them on GitHub (and with Apple via feedback) is via a GitHub Gist.

# Third Party Software

It's important to note that since Final Cut Pro 10.6.6 Apple has dropped FxPlug3 support.

When the effect or look you want to achieve can't be created with the filters or generators provided with Final Cut Pro or Motion, the FxPlug software development kit (SDK) allows you to write your own custom visual effects.

FxPlug is a compact, powerful image-processing plug-in architecture that lets you create unique, hardware-accelerated or CPU-based effects plug-ins with customized UI and onscreen controls.

In Final Cut Pro 10.6.5 and earlier, FxPlug3 plugins ran "inside" Final Cut Pro, and a bad plugin could crash Final Cut Pro.

However, since Final Cut Pro 10.6.6, only FxPlug4 is supported, and all FxPlug4 plugins are run "out of process" - meaning they're effectively their own application, and if they crash, Final Cut Pro doesn't.

Generally speaking if a FxPlug4 plugin crashes, then Final Cut Pro will just try restart it, and if it crashes 5 times or so, then it'll display the "this plugin is not responding" message.

All Workflow Extensions also run out of process.

For example, you can see all the different processes in Activity Monitor:

If you manually try and force quit a process, you'll see Final Cut Pro start it up again when needed.

What this means is that since Final Cut Pro 10.6.6, if Final Cut Pro crashes, it's NOT a third party FxPlug4 effect or a Workflow Extension - it's something in Apple's own code, and there's nothing third party developers can do about it, so there's no point emailing FxFactory, CoreMelt, MotionVFX, etc. to complain.

# Final Cut Pro 10.6.9

Here's a list of the 30 most recently added Final Cut Pro 10.6.9 bug reports:

The above list is pulled from our GitHub issues site.

# Final Cut Pro 10.6.8

Here's a list of the 30 most recently added Final Cut Pro 10.6.8 bug reports.

Some of these bugs may eventually be migrated to the 10.6.9 list once confirmed.

The above list is pulled from our GitHub issues site.

# Most Popular

Here's a list of the 30 most popular Final Cut Pro bug reports:

The above list is pulled from our GitHub issues site.

# Recently Added

Here's a list of the 30 most recently added Final Cut Pro bug reports:

The above list is pulled from our GitHub issues site.

# Discuss this page

© Copyright 2023 LateNite Films Pty Ltd. All rights reserved.