Lightning Aura Components Developer Guide

Introducing Aura Components
Quick Start
Creating Components
Using Components
Communicating with Events
Communicating Across the DOM with Lightning Message Service
Creating Apps
Styling Apps
Developing Secure Code
Using JavaScript
Working with Salesforce Data
Testing Components
Debugging
Performance
Reference
Lightning Component Library
System Tag Reference
JavaScript API
$A namespace
Action
AuraLocalizationService
Component
addEventHandler()
addHandler()
addValueHandler()
addValueProvider()
autoDestroy()
clearReference()
destroy()
find()
get()
getConcreteComponent()
getElement()
getElements()
getEvent()
getGlobalId()
getLocalId()
getName()
getReference()
getSuper()
getType()
getVersion()
isConcrete()
isInstanceOf()
isValid()
removeEventHandler()
set()
Event
Util
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

destroy()

Destroys the component and cleans up memory. After a component that is declared in markup is no longer in use, the framework automatically destroys it and frees up its memory. If you create a component dynamically in JavaScript and that component isn't added to a facet (v.body or another attribute of type Aura.Component[]), you have to destroy it manually using destroy() to avoid memory leaks.

Signature

destroy()