[bug report] FileChooser memory leak & cannot open native browseForDirectory dialog in release build in a Console Application in Windows 10

[ed95]

This is harmless, and isn’t a JUCE bug. See here:

Thread is causing memory leaks

I don’t know which thread you’re talking about, but it sounds like you misunderstood it. I’ve never said that leaks can be ignored if they’re small. That’d be bad practice. But this particular leak is just a side-effect of a Message object sitting on the message queue at the moment when your plugin was deleted. That means that the message never gets delivered, so its payload isn’t deleted. As I’ve explained on the (many!) other threads where I’ve talked about this, it’s not possible to force…