I just updated to the tip to fix (hopefully) the DrawableButton issue, and now I’m getting some new leaks I haven’t seen before and believe do not belong to me - it looks as if the MessageManager is leaking…?
*** Leaked objects detected: 1 instance(s) of class N4juce9HeapBlockIPNS_7MessageEEE
JUCE Assertion failure in …/…/…/…/…/rec/src/…/…/juce/juce_amalgamated.h, line 3296
Debugger() was called!
(gdb) continue
*** Leaked objects detected: 1 instance(s) of class N4juce14MessageManagerE
JUCE Assertion failure in …/…/…/…/…/rec/src/…/…/juce/juce_amalgamated.h, line 3296
Debugger() was called!
(gdb) continue
*** Leaked objects detected: 1 instance(s) of class N4juce9HeapBlockIPKNS_15MessageListenerEEE
JUCE Assertion failure in …/…/…/…/…/rec/src/…/…/juce/juce_amalgamated.h, line 3296
Debugger() was called!
EDIT: I put delete MessageManager::getInstance() in my shutdown code and now I get an assertion failure indicating that I’m leaking some sort of MessageListener object.
Perhaps I am leaking this MessageListener object and it’s keeping the MessageManager from being deleted, and that’s why I’m getting this slightly misleading error?