Wonder if anyone can help me out. I’m helping someone out with a bit of plugin code as they were unsure how to handle buffer writes in JUCE in comparison to the VST SDK approach etc.
The code is all sorted, however, I’m running into an issue in which the very first load of a fresh build crashes the PluginHost app. So if I scan for new vst’s and load the newly built version (after clearing the list of available plugins) I’m finding that the PluginHost crashes with the plugin in question as soon as I move focus from PluginHost to another app.
Yet if I then close PluginHost down and open again, reload the plugin (without scanning but still the same build) the crash does not occur.
It appears to be some issue on the message thread but I cannot work out where in the code it’s being caused.
Heres a stack trace at the point of the crash:
Plugin Host.exe!juce::MessageManager::dispatchNextMessageOnSystemQueue(bool returnIfNoPendingMessages) Line 118 C++
Plugin Host.exe!juce::MessageManager::runDispatchLoop() Line 130 C++
Plugin Host.exe!juce::JUCEApplicationBase::main() Line 244 C++
Plugin Host.exe!WinMain(HINSTANCE__ * formal, HINSTANCE * __formal, char * __formal, int __formal) Line 133 C++
Running on Windows 10 using the current master branch.
The exception thrown is an Access violation. Sorry I’m used to working in Linux but have quickly debugged this in VS on a work machine and haven’t a whole lot of experience using the debugger for cpp.
Any words of wisdom much appreciated.