Thanks for the suggestions. What I was looking for is a defensive programming technique to guard my service against memory exhaustion caused by other services/activities running on the device. The SDK has this to say about a service process:
"...so the system keeps them running unless there's not enough memory to retain them along with all foreground and visible processes". But are you implying that OutofMemoryError will not occur *before* a service is killed in a low memory situation? In other words, an OutofMemoryError will occur *only* when my own service eats up all the 16 MB default heap size. Then I don't need to worry about another service/activity squeezing the 16MB heap size. Is that true? doug -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
