There is no leak, I just verified myself. Your call to System.gc() does NOT guarantee that the GC will run. To check for leaks here is the procedure:
- Run the app - Run adb shell dumpsys meminfo | grep -A 12 name.of.the.app.processs - Look at the count of Activities and ViewRoots - Run DDMS - Force a GC on the app's process - Force a GC on system_server - Force a GC on the app's process - Run adb shell dumpsys meminfo | grep -A 12 name.of.the.app.processs - Look at the count of Activities and ViewRoots (Repeat these steps) You will see that while the number of Activities/ViewRoot does increase temporarily, it always goes back down the normal numbers. On Mon, Jul 6, 2009 at 3:01 PM, skink<psk...@gmail.com> wrote: > > > > On Jul 6, 6:33 pm, skink <psk...@gmail.com> wrote: >> however i read Toast's api docs again and found that ctor and/or >> makeText can use Activity context... so now i'm a bit lost here: is it >> a bug in Toast or docs shoukd be updated? >> >> thanks >> pskink > > hi, > > is it possible that nobody uses Toasts? > > can i consider memory leaks when passing Activity ctx as a bug (and it > will be fixed in some future release) or i have to change ctx to app > context? > > thanks > pskink > > > -- Romain Guy Android framework engineer romain...@android.com Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
