JUCE  v6.1.6 (6.0.8-1114)
JUCE API
Looking for a senior C++ dev?
I'm looking for work. Hire me!
juce::HeavyweightLeakedObjectDetector< OwnerClass >::BacktraceMapHolder Struct Reference
Collaboration diagram for juce::HeavyweightLeakedObjectDetector< OwnerClass >::BacktraceMapHolder:

Public Member Functions

 BacktraceMapHolder ()=default
 
 ~BacktraceMapHolder ()
 
String getFormattedBacktracesString () const
 

Public Attributes

BacktraceMap map
 

Constructor & Destructor Documentation

◆ BacktraceMapHolder()

template<class OwnerClass >
juce::HeavyweightLeakedObjectDetector< OwnerClass >::BacktraceMapHolder::BacktraceMapHolder ( )
default

◆ ~BacktraceMapHolder()

template<class OwnerClass >
juce::HeavyweightLeakedObjectDetector< OwnerClass >::BacktraceMapHolder::~BacktraceMapHolder ( )
inline

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.

Member Function Documentation

◆ getFormattedBacktracesString()

Member Data Documentation

◆ map


The documentation for this struct was generated from the following file: