Which plugin crashed or froze my session?
First check whether your DAW quit or is still running. Crashing sessions and freezing sessions can look similar when work stops, but they leave different evidence. That difference determines how to find the plugin responsible.
Freeze vs crash: is the DAW still running?
A crash is an unexpected quit. A freeze leaves the DAW open but not responding: a spinning beachball, a locked export, or a session stuck during load. People call both “a plugin crashed my session,” but the troubleshooting is different.
macOS writes a crash report when an app crashes, not merely when it hangs. Force-quitting a frozen DAW erases the live evidence. DAW Defrost captures the hang while the process is running; it cannot identify a plugin after the DAW has already quit.
After a crash: start with the report
Note the time and the action that triggered the quit. On Mac, open Console and look in Crash Reports for the DAW or a plugin host at that time. Use the DAW's own crash-report tools too; for Live, see Ableton's report locations and keep its log for support.
A third-party plugin appearing in the crashed thread is a useful lead. Confirm by testing a copy of the session without that plugin, and share the report with the vendor if needed. DAW Defrost does not parse logs, read crash reports, or analyze crash dumps.
During a hang: capture it, then isolate plugins
If the DAW froze but is still running, that is the time to capture it. On a supported Mac, DAW Defrost watches from the menu bar, checking responsiveness every 15 seconds. After 30 seconds of not responding, it snapshots the process and reads which plugin's code the threads are stuck in. A popup names the third-party plugin; a full report goes to Documents ▸ DAW Defrost Reports.
For manual troubleshooting after restarting, keep the original session and test a copy. Disable or remove suspected plugins, repeat the exact playback, export, or load that failed, then reintroduce plugins one at a time. If the session cannot load, use the DAW's plugin-disabled startup option where available, or temporarily move suspected plugin files out of its scan location with the DAW closed. Record what you moved so you can restore it.
Start with plugins added or updated near the first failure, but test rather than guessing. A vendor update or bypassing the confirmed plugin is often the fix. DAW Defrost names the cause; it does not repair the freeze or bypass anything automatically.
If your session won't open
If the DAW launches and stays running but hangs while loading the session, DAW Defrost can capture that load hang. If the DAW quits immediately, use the crash report or a safe-mode startup instead. A missing file dialog or slow load that still responds is not automatically a frozen plugin.
Ableton Live freezing or not responding
Try Option on Mac (Alt on Windows) while launching Live to disable plugin scanning until it opens. This is Ableton troubleshooting advice; DAW Defrost does not run on Windows. See the Ableton freeze guide for the crash-report and isolation steps.
Logic Pro spinning beachball
Shift-Control at launch opens Audio Units safe mode with validated AUs only. A crashed AUHostingService may have its own Console crash report. For a running hang, Defrost also inspects Apple's separate plugin hosts used by Logic Pro and GarageBand. See the Logic Pro freeze guide.
Pro Tools not responding or a plugin crash on Mac
If Pro Tools quit, start with the crash report and isolate the suspect plugin in a copy of the session. If Pro Tools stays open but freezes on playback, export, or load, DAW Defrost can capture the running hang on a supported Mac.
FL Studio freeze or project won't load on Mac
A project that leaves FL Studio running but not responding during load is a hang. An FL Studio plugin crash that closes the app needs crash-report troubleshooting instead. DAW Defrost captures the running Mac hang, not an event after FL Studio quits.
A Mac menu bar app for the missing evidence
DAW Defrost auto-detects the running DAW, including more than one at once. It requires an Apple silicon Mac (M1 or later) and macOS 13 or newer. It never touches the audio path, uses no meaningful CPU, and works locally without internet or uploads.
There is also a Check Now button for on-demand checks when playback stalls but the DAW still responds. The product page explains the report, supported DAWs, and requirements. The one-time $19 purchase includes DAW Defrost and Session BPM.
Common questions
How do I find which plugin crashed my session?
If the DAW quit unexpectedly, check its crash report or macOS Console, then test suspected plugins in a copy of the session. If the DAW is still running but frozen, DAW Defrost can capture the hang and name the plugin on a supported Mac.
Why are there no crash reports when my DAW froze?
A freeze leaves the DAW running but not responding. macOS writes a crash report when an app crashes, not merely when it hangs. Force-quitting loses the live process evidence.
What do I do if my session won't open?
If the DAW stays running but hangs during load, capture the hang or try manual plugin isolation. If it quits immediately, use a crash report or safe-mode startup. DAW Defrost only captures a running hang.
Does DAW Defrost fix frozen plugins?
No. It names the third-party plugin responsible for the freeze. The usual fix is a plugin update from the vendor or bypassing that plugin on the track.
Does it work with Ableton, Logic Pro, Pro Tools, and FL Studio on Mac?
Yes. DAW Defrost auto-detects those running Mac DAWs. It requires Apple silicon (M1 or later) and macOS 13 or newer; it does not support Windows or Intel Macs.
DAW Defrost + Session BPM. One-time purchase, no subscription. DAW Defrost requires an Apple silicon Mac (M1 or later) and macOS 13 or newer.
Get both apps for $19