Killing activities when memory gets short
Marco Pesenti Gritti
marco at marcopg.org
Sat Aug 7 20:37:13 EDT 2010
On 7 Aug 2010, at 21:08, Tiago Marques <tiagomnm at gmail.com> wrote:
> Just killing a random activity is a terrible idea becayse you don't want your product behaving like it's defective; the pop up idea is way more acceptable(and a lot better than having the system randomly behaving like it's crashed). Either way, this is the extremely important use of swap memory that doesn't exist here. I understand your engineering constraints on the hardware but randomly killing activities is poised to confuse users and cause people considering the hardware for deployment to think that you're selling them something defective/baddly manufactured.
As long as activities are saving and restoring properly it could be made pretty much transparent to the user. Of course that's easier said then done...
More information about the Devel