Skip to content

FCP 12.4 hangs permanently reopening a library: all 150 worker threads blocked on AU instantiation (DeRoom 2, macOS 27.2) #567

Open

Description

@alloffroadau-netizen

OS27.2 FCP 12.4 M5 Studio Ultra 96GB RAM

Apple Feedback Assistant ID: MISSING

DESCRIBE THE BUG:
Final Cut Pro hangs permanently while reopening a library after a restart. It opens the library, starts loading the event, then freezes and never recovers. I left it 588 seconds once. Force quit does not fix it because it repeats on the next launch. Deleting the FCP preferences (so it forgets the last open sequence) is the only thing that got me going. It happens intermittently, across different libraries.

The hang report shows FCP deadlocking itself on audio unit instantiation. The main thread is in restoreOpenDocuments > loadEditorForLastOpenSequence > TLKReloadOperation addOperations:waitUntilFinished, waiting for the timeline to finish loading. All 150 GCD worker threads (the report says the process hit the dispatch thread soft limit of 150) are blocked on a semaphore in FFSharedAudioUnit instantiateWithEffectID > FFAudioUnitEffect _requestMasterUnitForEffectActivation. FFSharedAudioUnitPoolUpdateQueue is also blocked on a semaphore in updateAudioUnitAllocationForFormatKey. With no free threads, nothing can complete, so it never recovers.

The AU host (AUHostingServiceXPC_arrow) had 151 instances of Accentize DeRoom 2 (2.0.4, AUv2) running, and it was the only third party plug-in loaded. The host process was idle (about 0.016s CPU in total, all threads waiting). The plug-in was not busy or hung. FCP was waiting on itself.


TO REPRODUCE:
I do not have a reliable repro, it is intermittent.

  1. Have a library whose last open sequence uses a third party AU effect (DeRoom 2) on many clips.
  2. Restart the Mac or quit FCP.
  3. Launch FCP so it reopens the last library and sequence.
  4. FCP freezes while loading the event.

Moving Accentize-DeRoom2.component out of /Library/Audio/Plug-Ins/Components and relaunching made the library open straight away.


EXPECTED BEHAVIOUR:
FCP opens the library and timeline. A slow or high-instance-count AU plug-in should never block the main thread and all worker threads forever. Instantiation should be limited, run asynchronously and time out, and the pool update queue should not be able to starve at background priority. A sandboxed out of process plug-in should not be able to leave FCP unrecoverable.


SCREENSHOTS:
None, it is a hang. Hang report (spindump) attached, trimmed to the Final Cut Pro and AU host sections.


SPECS:
Final Cut Pro 12.4 (454072)
macOS 27.2 (26B123)
Mac17,15, Apple silicon, M5 Studio Ultra, 96 GB RAM
Third party plug-in: Accentize DeRoom 2 v2.0.4 (com.accentize.DeRoom2), AUv2 component, /Library/Audio/Plug-Ins/Components/Accentize-DeRoom2.component
Hang duration: 588 seconds, event: hang


ADDITIONAL COMMENTS:
DeRoom is the trigger, but I think the underlying problem is in FCP's audio unit pool. Reported to Accentize as well. Has anyone seen this with other AU plug-ins used on many clips? Workaround: remove the plug-in component before launch, or delete the FCP preferences.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions