This is on mac OSX: The vst3 sdk includes a text host called VST3PluginTestHost. It is similar to auval, but also has a GUI. I remember using this host to test my plugins when I last did a release, but with the latest Juce sources (4.2.2+) I can no longer open a Juce-built plugin. With one of my plugins, the VST3PluginTestHost doesn’t even launch… so I tried the “Juce Demo Plugin”. When I try to create an instance of the demo plugin, the test host gets stuck in an endless loop using 100% cpu on one core. I tried looking at the problem with the XCode debugger and Instruments, but it’s stuck somewhere extremely weird. To me it looks like memmove if moving around tons of memory for no reason and never gets done. At the same time I see a bunch of SpinLocks related to String methods, but no plugin client code.
I’ve seen a similar issue in Garageband once, but in that case, the moving of memory at least got done after about 3 minutes.
Has anyone experience running their vst3 plugins in that VST3PluginTestHost? Have any of you seen similar endless-loop situations with memmove involved? Searching the web things seem to point at some form of compiler/runtime library configuration issue.
Before you fellow developers will hopefully post numerous replies, I’ll try to build with older Juce versions to find the breaking point with that host.