On Jul 30, 8:52 pm, Rud <[email protected]> wrote: > Are you running on the emulator or a device? There are some reports > that on the emulator, espeically in debug mode, memory is not GC'd > because the debugger is holding a refernece. I haven't experimented to > see if this is true but it is worth checking into.
If you have a debugger attached to an app process, objects the debugger is aware of will not be GCed in that process. This is equally true for device and emulator. See dalvik/docs/debugger.html: http://android.git.kernel.org/?p=platform/dalvik.git;a=blob_plain;f=docs/debugger.html;hb=HEAD > You might try calling the GC prior to reallocating your variables. Either they're reachable or they're not. Barring tricks with finalizers, objects that aren't reachable will not become reachable again, so whether you GC early or late doesn't matter. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
