我的单身人士会被杀死吗？

Question

I have an application where I create a foreground service to make sure a user initiated upload continues even if the user quits the app or app is killed by memory pressure.

Both the service and app use a singleton to pass data around. I know this is not the best solution, so kindly ask to refrain from comments about bad-bad singletons as the question is not in this but in the following:

When I close the app, my foreground service continues running and can access the singleton. Is there a risk of the singleton being garbage collected due to memory pressure or are there any other memory related risks of using a singleton in this case?

Answer 1

1. There is nothing bad about singletons. But as any other pattern or method it just could be used improperly.
2. Due to memory pressure or any other reason a system could kill your app. But your Service will be relaunched later.

Answer 2

1. Singleton pattern is a very useful pattern in the system due to that it is a static format. Exactly one object is needed to coordinate actions across the system. You dont need to worry about the duplication or you accidentally create multiple modules.
2. A foreground service is a service that's considered to be something the user is actively aware of(has focus) and thus not a candidate for the system to kill when low on memory. The skeleton object will not be killed.

Answer 3

Static variables are only destroyed when the application is killed. So they won't just randomly disappear while your service is running. However if your entire service restarts you do have to account for the possibility of not having the singleton when it restarts.