If you hit this, then you've leaked one or more objects of the type specified by the 'OwnerClass' template parameter - the name and stack trace of its creation should have been printed by the lines above.
If you're leaking, it's probably because you're using old-fashioned, non-RAII techniques for your object management. Tut, tut. Always, always use std::unique_ptrs, OwnedArrays, ReferenceCountedObjects, etc, and avoid the 'delete' operator at all costs!
References DBG, juce::HeavyweightLeakedObjectDetector< OwnerClass >::BacktraceMapHolder::getFormattedBacktracesString(), juce::HeavyweightLeakedObjectDetector< OwnerClass >::getLeakedObjectClassName(), jassertfalse, and juce::HeavyweightLeakedObjectDetector< OwnerClass >::BacktraceMapHolder::map.