When i wrote my image editor, i put the 'gallery/pick-list of images' activity (and other activities) into one process and the actual 'editor' activity in another. I needed to squeeze every bit of memory out of a process to make have a chance at having enough memory when editing full-sized images.
It did work for me :-). On Nov 4, 6:49 pm, Mark Murphy <mmur...@commonsware.com> wrote: > On Thu, Nov 4, 2010 at 6:20 PM, Matt Quigley <matthew.quig...@gmail.com> > wrote: > > Using two processes would take up more total memory when they were > > active at the same time. However, sometimes components are foreground > > and background and therefore are active in, some components are active > > frequently or all the time in the background such as Services and > > BroadcastReceivers, and some only when in the foreground such as an > > Activity. Some components take 5000% more memory than others. It > > would indeed be stupid to double memory to allow the OS to more easily > > kill half of it, but that is not what I was implying. > > My understanding is that the Dalvik GC engine can yield RAM back to > the OS. Hence, it is unclear that you are really improving the memory > situation with your approach. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > Android 2.2 Programming Books:http://commonsware.com/books -- 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
