Tuesday, April 23, 2013

[android help] Android : Process has died / AsyncTask HTTP get


The Low Memory: No more background processes is a dead giveaway in your case. The device ran out of memory. When it does, it stops processes. It stops them in following order:


  1. Processes without any activity or service, i.e. applications that were put on background and stay running in case the user will need them again.

  2. Processes with background services like checking email.

  3. Processes with foreground services like background download or playing music player.

  4. Processes with foreground activities, i.e. the application being used.

Apparently your application loads too many bitmaps and exhausts all memory. The system first stops everything that is not needed, but when you keep loading bitmaps, it has to kill things that are needed too. The background download service goes first, because it's in the third case above.


You simply have to make sure you never have many bitmaps in memory at the same time. Note, that flash memory is rather fast and using lot of memory slows the device down itself, so it's unlikely that keeping more than the bitmaps on display and a few most recently used ones in memory helps anything.



.

stackoverflow.comm

No comments:

Post a Comment

Google Voice on T-Mobile? [General]

Google Voice on T-Mobile? So I recently switched from a GNex on Verizon to a Moto X DE on T-Mobile. I had always used Google Voice for my v...