Hi, Once upon a time many years ago, it was useful to run separate Processes in Android apps when dealing with large image files that might cause OOM explosions as the Bitmap API was quite memory constrained & somewhat unpredictable.
By partitioning an app & doing such image processing in (background) Services running in separate Processes you could avoid the situation where your entire app would die in the event of an uncaught / unrecoverable OOM. These days with the much improved Bitmap API & more memory that extra effort no longer seems necessary. Regards On Wednesday, August 12, 2015 at 4:16:39 PM UTC+10, Chris Pick wrote: > > I am always curious as to why developers are trying to work so hard to get > around normal android life cycles.. It might help if you explained what you > are trying to achieve and why you are doing this option. > > You might find a better answer.. > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
