Angular Destroy & jquery Destroy

The purpose of the destroy is for memory leaks, which can have an impact on performance.

Angular scope triggers destroy when dealing with element removal, and the invocation logic is used as jquery.

There is one thing you can refer to in CK Editor.

CK Editor has its own destroy event, changing the number of repeat CK Editor in Ng-repeat, resulting in a bug (no element found). Why?

Because the change in the ng-repeat will trigger the wash off element first, then trigger the destroy, wash off the element will also trigger destroy, but the element itself, not scope. The bug appears because of the destroy event that wrote the wrong element, but instead wrote the scope destroy callback element destroy caused no element to be found!

Angular Destroy & jquery Destroy