I’m a big fan of the built in leak detection of juce, but all of a sudden (?) it has started to fail me. I think… Or am I suffering from some sort of memory corruption?
- On quit, I get a report from VS2010 that there was a bunch of memory leaks. I can roughly track them to a certain class.
- I don’t get any indication from juce that anything is leaked.
- I seem to be able to track all destructors in the so called leaked objects.
- When deliberately leaking a juce object, juce does properly report it.
All of the above indicate that VS2010 is giving me false positives, but I don’t recall seeing these earlier.
Does anyone have a tip of how I can track down the problem/actual problem? I’m at a loss!
Supposedly, on quit, juce is reporting leaks before VS2010, so something must be wrong, which juce doesn’t see?
Thanks in advance, Michael