Which Plugin Is Freezing Ableton Live? How to Isolate a Hang on Mac

This workflow focuses on Live remaining open but frozen on a Mac. If the application quits instead, use the general crash-and-freeze guide for the report distinction. For the immediate recovery decision during a beach ball, read Live not responding on Mac first.

Write down a reproducible trigger

“Freezes sometimes” is difficult to test. “Open the second synth’s editor after playing the chorus” gives you something to repeat. Note the playback position, plugin preset, whether transport was running, and whether the editor was visible. A plugin can behave differently during playback, offline rendering, and loading a saved state.

Also note whether the issue began after a plugin, Live, or macOS update. Keep that observation as context, not a verdict. A new version can expose a problem elsewhere in a chain. Avoid changing buffer size, sample rate, plugin format, and preset simultaneously; you will lose the comparison that makes the test useful.

If reproduction requires a particular audio input or MIDI controller, include it in the notes. If it occurs without playback, say that too. The distinction helps separate an audio-processing load issue from a problem with a window, preset, or initialization step.

Use track CPU meters as clues while Live still responds

In Live 11 and later, the per-track CPU meter or Performance Impact display helps locate tracks with heavier processing. Watch the suspected passage while the application is responsive. A dense instrument rack, long serial effect chain, or oversampled processor may stand out. Compare the passage with the device active and inactive in your test copy.

A high meter is a performance clue, not a plugin-hang diagnosis. A costly synth may consume lots of processing time and remain perfectly functional. Conversely, a plugin can get stuck without first becoming the highest CPU consumer. Once Live is not responding, you cannot rely on a frozen meter to describe what its threads are doing now.

For improving a responsive but overloaded session, use the CPU reduction guide. Keep that performance work separate from proving which device causes the lockup. Lowering total load may improve headroom without resolving a specific repeatable hang.

Preserve the hang when it is available

A live hang contains evidence that disappears when you force-quit. On an Apple silicon Mac with macOS 13 or newer, DAW Defrost can snapshot Live while it is running but unresponsive. It checks with macOS every 15 seconds and captures after 30 seconds of not responding, reading which plugin’s code the threads are stuck in.

It shows a popup naming the third-party plugin and saves the full technical report to Documents ▸ DAW Defrost Reports. If playback has stalled but the interface still responds, there is also a Check Now button for an on-demand inspection. Capture is useful before you end the process, not after reopening the Set.

DAW Defrost does not read crash reports or logs, fix the freeze, automatically bypass plugins, or update them. It needs an M1 or later Mac; Intel and Windows are unsupported. It operates locally without uploads or internet and does not touch the audio path. Use the named plugin as the starting point for your controlled follow-up and vendor report.

Isolate in a copy of the Set

Save a separate troubleshooting version and retain the original project. Start with the named or most strongly suspected device. Remove it from the test version, repeat the exact trigger, and record whether the hang returns. Do not overwrite the original arrangement with a stripped-down diagnostic experiment.

When you have many suspects, reduce the search in groups. Create independent copies with different groups of devices removed, while preserving the routing needed for the test. Once one group makes the problem disappear, narrow within that group. A changed result is meaningful only if the original trigger still occurs under comparable conditions.

Bypass is a useful first comparison, but it is not identical to removing a plugin from a test Set. A bypassed device can still be instantiated and have a window or saved state. If the hang occurs on opening or preset recall, test removal in the copy as well. Reintroduce suspects one at a time once you find a stable baseline.

Test one instance in an empty Set

Create a new, empty Set with a single instance of the suspect. Try the same preset and action, using the same audio or MIDI material when it matters. If this smaller example hangs, you have a much easier reproduction to describe to the vendor. If it does not, the original routing, other instances, or an interaction may matter.

Keep both outcomes in your notes. A clean empty-Set test does not prove the plugin is innocent in the full arrangement. Try adding the smallest necessary part of the original setup until the symptom returns. Do not send an entire client production when a minimal test will demonstrate the problem.

Check AU, VST2, and VST3 deliberately

Ableton advises using one format of a given plugin throughout a Set rather than mixing AU, VST2, and VST3 versions of that same plugin. Check what your instances actually use; matching product names do not guarantee matching formats. See Ableton’s plugin troubleshooting guidance for the official format and isolation advice.

If you compare another format, do it in a separate copy and check presets, automation, and routing after replacement. Do not assume an AU preset or automation lane transfers perfectly to VST3. Render a listening reference before making large substitutions so you can compare the musical result as well as stability.

Turn the finding into a useful next step

Check the plugin vendor’s compatible updates and supported Live/macOS combinations. Report the plugin version and format, Live version, macOS version, exact trigger, and whether an empty Set reproduces it. Attach the Defrost technical report when available. A clear sequence is more actionable than a screenshot of an unresponsive window.

After updating or replacing the device, repeat the original test in a copy of the full production. Confirm playback, editor actions, and any export that previously failed before returning to the original workflow. The broader why Ableton freezes guide covers other suspects if the plugin tests do not explain it. Find related articles in the studio blog.