When I load a VST in a tracktion engine project, I always leak memory when the project closes. I typically get something like this:
Cleaning up temp files..
*** Leaked objects detected: 1 instance(s) of class AttributeList
JUCE Assertion failure in juce_LeakedObjectDetector.h:90
*** Leaked objects detected: 1 instance(s) of class VST3HostContext
JUCE Assertion failure in juce_LeakedObjectDetector.h:90
AM_MemoryRecord closing down with 338 allocations vs 331 freed
AM_PreferencesAudio::destroy instance destroyed
AM_PreferencesAudio::~AM_PreferencesAudio(), instanceCount after destruction: 0
4 allocations left
Program ended with exit code: 0
What’s the right way to cleanup/free resources in a project with external plugins?
I observed the same problem, it seems only to occur when scanning a new plugin (also juce plugins IIRC.). When there was no new plugin, the leaks were gone for me.
So at least the harm it can do is very limited.