No longer want com.xxx.xxx (pid 1970): hidden # 16

posts by HellDevil on 2012-10-24 17:51:01 Edit

Hello everyone, I wrote the application, and the application has a separate service, application and service that is both processes.
When I start my app, this service will be started up, it will, and this app has some data on the interaction. When I run my program for a long time, such as 30 minutes or more, I found that my service would be to kill off the system prompt is: No longer want com.xxx.xxx (pid 1970): hidden # 16, I google the next , a foreigner's article says it is android2.2 AM (activitymanager) added mechanism for a long time to kill background processes exist, in order to save memory and other resources. But it said before that he was an "insufficient memory when the system is in the state."
I wonder, there are systems to kill my serivce, in the end is such a mechanism (to kill long running time of service), or because I have a memory leak causes memory is not enough to trigger the kill service behavior ah. Big Brother this mechanism there is to know it? I did not see my log in sign of insufficient memory prompted. . .

If it is because the general mechanism AM, I do not want to be killed how to do. . . Do not say anything persistent, this is the need system privileges. I was an ordinary application, I do not want my service to run for a long time were killed.
If it is due to a memory leak so I went to check the next. . . .<-! Main posts under Banner (D4) -><-! Posts under the main text (D5) ->
Reply:
Can improve service levels, this may be killed to reduce the possibility of immortality in that build. On the Internet trying to find the code
Reply:
Useless, if not the foreground process, there is always likely to be killed
Reply:
Man child, this error in the source file has defined ActivityManagerService.java, you can look