**Makes Cubase 15 on Mac crash at Quit
The crash is in Synthesizer V Studio 2 Pro (the VST3 plugin, v2.3.0), not Cubase itself.**
What the log shows
-
Thread 28 triggered the crash. It, and threads 21–29, are all background threads belonging to synthv-studio. Each one is exiting and running its thread-local cleanup. That cleanup calls std::terminate() and then abort(). In practice this usually means an exception was thrown from a destructor, or the destructor touched something that no longer exists.
-
The main thread (thread 0) is already in exit(). You chose Quit, AppKit called terminate:, and the C runtime is now tearing down the global objects of every loaded library.
-
It’s a race between those two. The process is dismantling shared state while Synth V’s worker threads are still alive. When those threads finish, their cleanup code hits already-destroyed objects and aborts. This is a classic “plugin didn’t stop its thread pool before process exit” bug.
1 Like
Ok, so this is a memory leak that happens when using Synth V with either Ara2 and Ara2 bridge. I don’t know what OS you’re using, but I’m on a Mac, and I use multiple DAWs. So, this happens in all the DAWs with Ara2 that I have installed where I’m using Synth V with Ara2 (Reaper, Studio one, Cubase and even FL Studio which has a specific “FL Link” created in partnership with DreamTonics) but doesn’t happen in the ones with out Ara2 (Bitwig, Abelton and Logic. Which, to be clear DOES have it in Rosetta mode. But like…say what?) and to be clear: this doesn’t affect your project nor internal Synth V session. All it means is that let’s say you have a project with Synth V in Ara2, then you close it out and move on to another project. In theory, when you close down the project with Synth V with ara2 it should close down that instance of Synth V and clean the memory. But it’s not really do yhat. It sort of lingers. And let’s say you’re working on the project with Synth V Ara2, and the close out the app. The same lingering thing is happening right before you close. But from what ChatGPT tells me is that one claims there’s still memory that needs to be cleaned up while the other says there’s nothing to be cleaned up and then…crash. However, reports have show that the memory is cleared up regardless, so it’s not like affecting your computer.
What this means for you and me: send crash reports directly to the dev team via the support page on the Dreamtonics site and not here. Apart from announcements, it’s been reported that the dev team doesn’t really interact with people here, as I’m sure they’re swamped and can only make the time for the with the support page emails. They mentioned that this memory leak was something that was cleaned up for Mac users in the release notes. But I don’t think it was the same thing now. Anyway, you helped me to remember to send my crash reports as well
1 Like