I’m having a problem with the VST3PluginTestHost not calling my plugin’s destructor.
My plugin spawns some threads to do IO work occasionally (to keep the processing thread IO free). This thread is joined during my destructor, but this is never called - this leaves the thread running on what eventually becomes garbage memory, which then causes a crash.
I can reproduce this behaviour 100% reliably when I remove my plugin from the VST rack in VST3PluginTestHost. Quitting the test host does not cause the crash.
Oddly, I do not see the destructor in the plugin lifecycle diagram on the (frustratingly sparse…!) VST3 documentation pages. Does this mean the destructor is not guaranteed to be called? When I run my plugin in Cubase, it’s generally fine - although Windows test machines occasionally crash on quitting cubase, or on session close.
It is entirely possible that the code base I’m working with isn’t doing something right, but I’ve been chasing this bug for a few days, and I can’t find anything.
Any help would be much appreciated.