Memory leakage caused by threads and Memory leakage caused by threads

Memory leakage caused by threads and Memory leakage caused by threads

Cause Analysis: similar to the reasons in the above cases, we developed an anonymous internal class Runnable, which has an implicit reference to the current Activity. If the internal tasks of Runable are not completed during Activity destruction, the memory resources of the Activity cannot be recycled, resulting in Memory leakage. The correct method is to use static internal classes as follows:

In the above Code, the static internal class MyRunable is customized to implement Runable and then instantiated when used.