I’ve been chasing a brain-melting, keyboard smashing bug for the last three days where the leak detector has been firing off in one class no matter what I do - even if I just do a local allocation on the stack, as soon as the object goes out of scope I get a dangling pointer leaked object assertion claiming I’m trying to double
delete which obviously makes no sense.
The base class uses the
JUCE_DECLARE_NON_COPYABLE_WITH_LEAK_DETECTOR macro, as does the derived class. Looking through JUCE code, I couldn’t find any instances of base classes using this macro. I recognize the overhead + redundancy of having two instances of the leak detector in the class hierarchy, but is it actually harmful to do so? If so, can we get some documentation on it so nobody else has to endure the debugging suffering I have experienced?