Before 5.0.2, whenever my plugin exited it did so cleanly. Visual Studio 2017 would then output three minor leaks into the output window (only 16-24 bytes, and only three of them). I figured it must be some legacy code of mine that I’ll clean up later.
Since the update to 5.0.2 suddenly an assertion fails that tells me that one StringArray was leaked. But I don’t use the StringArray class. This tells me that someone added the leak-detector to a juce class somewhere and it’s triggering now. But I have no idea where to look etc.
Does somebody from the JUCE developers remember adding a leak-detector recently, to a class that didn’t have one before?