2014-05-11 14:00 GMT+02:00 Piren <gpi...@gmail.com>: > Android has this particular annoying and weird behavior: Once the heap > inflates to a certain size, no matter how much of it is actually used, you > can no longer allocate files that are larger than the remaining memory. > my guess, you're there. > > you should make sure your previous activities use as little memory as > possible and make it a habit of unloading memory which might not be > necessary once activities are changed. This is especially true in apps that > store large bitmaps and even more noticeable if you also have lots of small > objects (memory fragmentation + large bitmaps = OOM exceptions)
I have inspected the code as Kostya mentioned, and i haven't seen anything what looks like a leak, all the memory was released after causing a gc manually. And i carefully checked every activity and its fragments. I only come to the conclusion that what you said must be the case i have no other answer for that. So will change the behavior of opening lots of activities. But in future it should be wise considered in the concept. Thank you for all readers and who respond. Daniel -- 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.
