Start by noting the action that preceded the stall: opening a plugin editor, switching a preset, loading a Set, exporting, or connecting hardware. That detail matters more than a general description like “Live crashed.” Keep the time and the Set name in a quick note while the event is fresh.
First, look for actual progress
A large sample instrument can need time to load. A first plugin scan after an update can take longer than your normal startup. A complex export may also make the interface feel sluggish. Look for changing progress text, an advancing export indicator, or other signs that the task is moving. Avoid repeated clicks that queue more commands.
Give an unusually heavy operation more room than a routine edit. There is no universal timeout that proves a hang: your storage, samples, plugins, and Set size all matter. If progress continues, waiting is usually more sensible than interrupting it. If an operation that is normally quick stays unchanged and the interface cannot respond, investigate a possible hang.
You can check whether other Mac applications still respond. If everything is sluggish, consider broader resource or storage pressure rather than assuming one plugin is responsible. Activity Monitor can provide context, but a high CPU percentage alone does not establish that Live is hung. A stalled thread can also exist without a dramatic CPU reading.
Distinguish not responding from an unexpected quit
Open the Mac’s Force Quit Applications window from the Apple menu to inspect Live’s status. Seeing “not responding” while Live remains open supports the hang path. Opening that window does not require you to force-quit immediately. Apple explains force-quitting an unresponsive app, including the risk of losing unsaved changes.
If Live disappeared or displayed an unexpected-quit message, the process has already ended. That is the crash path. Use Ableton’s crash troubleshooting and preserve the crash report. The same symptom description from a collaborator can refer to either state, so ask what remained on screen.
An audio dropout is another state entirely. If transport controls and menus still work but playback crackles, start with the CPU and performance workflow. A responsive application with missed audio deadlines is different from a locked interface, even if both interrupt the session.
Preserve the running evidence before force-quitting
If you want to know which plugin is stuck, do not immediately end the process. Force-quitting destroys the live-process evidence. macOS creates a crash report for a crash; a hang is not the same event simply because you eventually terminate it. A screenshot of the beach ball records the symptom, but it cannot identify the code holding up the session.
On an Apple silicon Mac running macOS 13 or newer, DAW Defrost can inspect Live while it is still running and frozen. It asks macOS about responsiveness every 15 seconds and snapshots a DAW after it has stopped responding for 30 seconds. That is approximately when capture becomes available, not a promise of a popup at an exact instant after your click.
The app reads which plugin’s code the threads are stuck in, names the third-party plugin in a popup, and saves a full technical report to Documents ▸ DAW Defrost Reports. It runs from the menu bar, needs no internet, uploads nothing, and never touches the audio path. Its Check Now button offers an on-demand check when playback stalls but Live still responds.
DAW Defrost names the cause; it does not fix the freeze, bypass a device, or install an update. It cannot read crash logs or reconstruct a session after Live has quit. It requires an M1 or later Mac, so it is not an option for Intel Macs or Windows machines. Keep the report before taking the recovery step.
Recover deliberately when waiting no longer helps
If the session remains unusable and you need to proceed, force-quit Live using Apple’s documented method. Unsaved work can be lost. On reopening, handle any recovery prompt carefully and keep a separate recovered version before experimenting. Do not overwrite your only original just to see whether the same operation fails twice.
For a plugin-related restart, Ableton’s documented launch method is to hold Option on Mac while opening Live until startup completes and the splash pane closes. This disables third-party plugin scanning for that launch; the next restart restores scanning. It is a troubleshooting step, not a repaired session.
If the affected Set opens this way, save your experiments separately. Record the suspected plugin’s name, format, and version before removing or replacing it in the test copy. If the only problem is opening a particular project, continue with the loading-a-Set workflow rather than repeatedly opening the original.
Treat a launch hang differently from a playback hang
When Live hangs before you can get to a Set, an interface, hub, drive, or driver may be involved. Ableton’s slow-start and launch-hang guide recommends shutting down, disconnecting external USB and Thunderbolt devices, restarting, and testing launch. Reconnect devices individually between tests to identify a pattern.
Follow that sequence rather than pulling a drive during a write. Keep the test project on local storage if you are temporarily removing the drive it normally uses. A successful launch without hardware is a useful lead; it does not automatically prove the interface itself is defective. Cables, hubs, drivers, and compatibility all deserve a controlled check.
Use the next stable opening to prevent a repeat
Check compatible updates for Live, macOS, plugins, and device drivers. Read vendor support notes before changing a working production system, especially during a deadline. Keep a note of what changed and test the action that originally stalled. Updating everything without a repeatable test can leave you unsure which change mattered.
Try the suspect alone in an empty Set, then in a copy of the full arrangement. Ableton’s plugin troubleshooting guide provides official isolation guidance. Include the reproduction steps and technical report when contacting the vendor. For broader background, read why Ableton freezes, or return to the studio blog.