juce::HeavyweightLeakedObjectDetector< OwnerClass >::BacktraceMapHolder Struct Reference

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!

Member Function Documentation

getFormattedBacktracesString()

template<class OwnerClass>

String juce::HeavyweightLeakedObjectDetector< OwnerClass >::BacktraceMapHolder::getFormattedBacktracesString ( ) const

inline

Member Data Documentation

map

template<class OwnerClass>

BacktraceMap juce::HeavyweightLeakedObjectDetector< OwnerClass >::BacktraceMapHolder::map

---

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

• /home/runner/work/lmms/lmms/plugins/CarlaBase/carla/source/modules/juce_core/memory/juce_HeavyweightLeakedObjectDetector.h