Android false exit is not a rogue action

About androidProgramAt present, we do not use the system. Exit (0) or killprocess mechanism, but directly exit with activity. Finish. Therefore, when the memory is sufficient, the process tool will find that our program is still in the memory after exiting. PreviousArticleI also said that this is determined by the mechanism of memory management and activity lifecycle of Android, which is understandable.

But some people say that there will be a little white who thinks that our program is too old to occupy the background, especially when we use 360 to see your process, it looks like a rogue action. In addition, I remember someone telling me that he has tested other common programs, such as QQ, And will automatically quit. Why can't you do it? I am a little worried. However, I actually tried it today. I didn't have it at all, and QQ didn't exit completely. After it quit, I still can use tools to see it (I used qq For pad on my mobile phone ). Then I tested several other programs, such as Sina Weibo and Android optimization masters, and found that they also quit falsely and the process was still in progress. I guess others said that he would quit on his cell phone, probably because his machine ran too much memory. My sub-machine has MB of idle memory for testing.

Then I tried to find that if there is only one rootactivity, you can use system. exit (0) or killprocess exit. However, if you activate multiple activities and do not have the Administrator permission, you cannot exit (I tried it on Android 2.3 ). Developers who are particularly entangled in false exit may consider using this root activity to force exit. However, this destructive operation is obviously not recommended, maybe later versions of the SDK will block this method.

Therefore, the conclusion is that false withdrawal is a normal action and international practice. Normal false withdrawal is not a rogue action. We should be confident that we may leave without having to say a few words to the white guys.