How AngualrJs solves the pitfalls encountered in clearing timers

This article mainly introduces the pitfalls encountered by AngualrJs clearing timers. Friends who need it can refer to it. I hope it can help everyone.

I discovered a strange problem today. The timer placed in the custom instruction is still executing on another page after the page jumps. This is definitely not possible and will affect the system. performance.

I used the native method window.onunload in Angular but it didn’t work, so I had to use Angular’s own method $destroy. This page jumps and the DOM structure changes, the timer can be cleared.

var timer = setInterval(function(){ $scope.$apply(function(){ //这里是想要定时刷新的逻辑 }); },3000); $scope.$on('$destroy',function(){ if (timer) { clearInterval(timer); timer = null; } });

Let me talk here, because I use the nativesetTimeout()andsetInterval()functions in javascript, so when clearing The corresponding areclearTimeout()andclearInterval(), the angular timer is$timeOutand$interval, so the clear corresponding is$timeOut.cancel()and$interval.cancel(),

must correspond one to one. Inconsistencies will not be cleared.

Related recommendations:

Javascript timer implements progress bar function

The above is the detailed content of How AngualrJs solves the pitfalls encountered in clearing timers. For more information, please follow other related articles on the PHP Chinese website!