When a plugin crashes
What Studio does when your plugin crashes or hangs in the preview, and how to find the line that caused it.
Studio catches your plugin's crashes, so the preview stops but Studio keeps running.
After a crashLink to this section
A notice says where it crashed, for example during audio processing or while opening its window.
- Details shows the call stack. Click a line to open it in the editor.
- Fix It (with an agent set up) sends the crash and its call stack to the agent.
- Open Error Line in Details (or Open on a notice with no call stack) goes to the line the error names.
Fix the code and build again; the new build loads into the preview. Common causes are reading past the end of a buffer, dividing by zero, and using a value that was never set.
Call stacks show line numbers when Line numbers in crash reports is on in Settings, Local Build (it is by default). Studio keeps the debug info beside the build, never inside the plugin, up to 1 GB.
If the plugin hangsLink to this section
If your plugin's audio processing doesn't return within about 5 seconds, Studio marks it stuck: Restart Studio to preview again.
Crashes Studio can't catchLink to this section
A few crashes close Studio itself: a crash on a thread the plugin started itself, or on Windows a Rust panic or C++ abort. The next time Studio starts, it says what happened, with Fix It and Open when it knows the line.
macOS: WebView buildsLink to this section
On macOS, an NIH-plug build with a WebView window that crashed after its window opened can't be loaded again in the same session. Build again to preview it.