The additional processes are created by demand (e.g. if you open the calendar). The increasing memory consumption comes from the fact the Java is not able to release (heap) memory back to the system. That's why google has implemented the ActivityManager, which from time to time kills the whole process only to restart it later with a lower memory footprint. That is exactly what the task killer app try to do, which is kind of redundant.

The ActivityManger does it's job pretty good on my Galaxy S with only 329 MB RAM available to the system. I never needed no task killer. But, this is only a workaround for resource constrained devices like smartphones. Current high-end android devices have up to 1GB of memory or more, so that the ActivityManger will become more and more out of work.

The additional processes are created on demand (e.g. if you open the calendar). The increasing memory consumption comes from the fact the Java is not able to release (heap) memory back to the system. That's why google has implemented the ActivityManager, which from time to time kills the whole process only to restart it later with a lower memory footprint. That is exactly what the task killer app try to do, which is kind of redundant.

The ActivityManger does it's job pretty good on my Galaxy S with only 329 MB RAM available to the system. I never needed no task killer. But, this is only a workaround for resource constrained devices like smartphones. Current high-end android devices have up to 1GB of memory or more, so that the ActivityManger will become more and more out of work.